-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
server: TestUpgradeHappensAfterMigrations failed [unexpected stopped rangefeed processor] #76649
Comments
|
cc @cockroachdb/kv-prs for triage |
I was able to get pretty good repros with
Usually would fail pretty quick, but sometimes it could take 3-5 minutes to hit the bug. |
This was bisected to #76445 in #76655 (comment). |
Reverting f048ab0 makes this much less likely to trigger. I suspect because of this client-side change: f048ab0#diff-063a1c1eae06f7b653f7f19bdb2f948df949b0039a7d6bcfb6194e53829294e0R283-R290 The old code would check the stopper before sending the However, even after reverting that change, I still got |
I think I found the problem.
Because cockroach/pkg/util/stop/stopper.go Lines 459 to 461 in 168c3e3
The condition there is: cockroach/pkg/util/stop/stopper.go Line 262 in 168c3e3
cockroach/pkg/util/stop/stopper.go Lines 598 to 601 in 168c3e3
If this happens, then it gets caught by the cockroach/pkg/kv/kvserver/replica_rangefeed.go Lines 411 to 413 in 0233176
However, cockroach/pkg/util/stop/stopper.go Lines 526 to 529 in 168c3e3
The following sequence of events is therefore possible:
I'll make |
server.TestUpgradeHappensAfterMigrations failed with artifacts on master @ 512320f0d3c6230edcbe8ca6eab33ed9183bfbfb:
Help
See also: How To Investigate a Go Test Failure (internal)
Parameters in this failure:
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: