-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changefeedccl: Test demonstrating changefeed inhibiting node shutdown. #82767
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Treat NodeUnavailable error as a retryable changefeed error. NodeUnavaiable error may be returned by changefeed processors if the node is being shutdown/drained. However, this error return is racy. Sometimes, the coordinator would see "rpc context cancellation" error instead -- in those cases it would treat the error as retryable. However, sometimes it is possible to get this error propagated (for example: when server shutdown races with starting up kv feed, which uses Stopper, whcih may return NodeUnavailable error if it's being shutdown). Release Notes: None
Informs cockroachdb#70433 Permanet fix is being tracked by the above issue. This is a temporary fix to ensure that change aggregators cancel their context when the server quiesces so that the server shutdown is not inhibited by the running changefeeds.
Full fix tracked in cockroachdb#82765 This test demonstrates that running changfeeds inhibit node shutdown. The issue is on the dist flow side. This is a temporary fix. The test itself takes more than 1 minute to run. This is the reason why it's being pushed as a proof of concept PR. However, it does demonstrate the issue; and that the context cancellation upon node shutdown added in change aggregator fixes the issue. Once we determine the cause of this test taking so much time, then it can also be added. Release Notes: None
miretskiy
pushed a commit
to miretskiy/cockroach
that referenced
this pull request
Jun 10, 2022
Informs cockroachdb#82765 Permanet fix is being tracked by the above issue. This is a temporary fix to ensure that change aggregators cancel their context when the server quiesces so that the server shutdown is not inhibited by the running changefeeds. The test for this functionality is not being merged due to the fact that it takes too long to run; however, the test can be seen here: cockroachdb#82767 Release Notes (enterprise change): Ensure running changefeeds do not inhibit node shutdown.
miretskiy
pushed a commit
to miretskiy/cockroach
that referenced
this pull request
Jun 13, 2022
Informs cockroachdb#82765 Permanet fix is being tracked by the above issue. This is a temporary fix to ensure that change aggregators cancel their context when the server quiesces so that the server shutdown is not inhibited by the running changefeeds. The test for this functionality is not being merged due to the fact that it takes too long to run; however, the test can be seen here: cockroachdb#82767 Release Notes (bug fix): Ensure running changefeeds do not inhibit node shutdown.
miretskiy
pushed a commit
to miretskiy/cockroach
that referenced
this pull request
Jun 13, 2022
Informs cockroachdb#82765 Permanet fix is being tracked by the above issue. This is a temporary fix to ensure that change aggregators cancel their context when the server quiesces so that the server shutdown is not inhibited by the running changefeeds. The test for this functionality is not being merged due to the fact that it takes too long to run; however, the test can be seen here: cockroachdb#82767 Release Notes (bug fix): Ensure running changefeeds do not inhibit node shutdown.
craig bot
pushed a commit
that referenced
this pull request
Jun 14, 2022
82489: sql: disallow adding column as primary key r=jasonmchan a=jasonmchan Previously, the behavior of ALTER TABLE ... ADD COLUMN ... PRIMARY KEY was undefined. With the legacy schema changer, this statement would appear to succeed, but it would break the new schema changer. This commit changes this by returning an explicit error. In the future, we should support this statement if the table's primary key was originally the default rowid primary key (see #82735). Fixes #82489 Release note: None 82768: changefeedccl: Do not inhibit node shutdown r=miretskiy a=miretskiy See individual commits for details: * Ensure running changefeed do not inhibit node shutdown (Informs #82765) * Treat node unavailable error as retryable. Test not being merged as part of this PR -- see #82767 Release Notes (bug fix): Ensure running changefeeds do not inhibit node shutdown. Release Notes (bug fix): Treat node unavailable error as a retryable changefeed error. Co-authored-by: Jason Chan <[email protected]> Co-authored-by: Yevgeniy Miretskiy <[email protected]>
miretskiy
pushed a commit
to miretskiy/cockroach
that referenced
this pull request
Jun 14, 2022
Informs cockroachdb#82765 Permanet fix is being tracked by the above issue. This is a temporary fix to ensure that change aggregators cancel their context when the server quiesces so that the server shutdown is not inhibited by the running changefeeds. The test for this functionality is not being merged due to the fact that it takes too long to run; however, the test can be seen here: cockroachdb#82767 Release Notes (bug fix): Ensure running changefeeds do not inhibit node shutdown.
miretskiy
pushed a commit
that referenced
this pull request
Jul 5, 2022
Informs #82765 Permanet fix is being tracked by the above issue. This is a temporary fix to ensure that change aggregators cancel their context when the server quiesces so that the server shutdown is not inhibited by the running changefeeds. The test for this functionality is not being merged due to the fact that it takes too long to run; however, the test can be seen here: #82767 Release Notes (bug fix): Ensure running changefeeds do not inhibit node shutdown.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Full fix tracked in #82765
This test demonstrates that running changfeeds inhibit node shutdown.
The issue is on the dist flow side. This is a temporary fix.
The test itself takes more than 1 minute to run. This is the reason
why it's being pushed as a proof of concept PR.
However, it does demonstrate the issue; and that the context
cancellation upon node shutdown added in change aggregator fixes the
issue.
Once we determine the cause of this test taking so much time, then
it can also be added.
Release Notes: None