-
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
sql/flowinfra: panic in rangefeed.(*CatchUpIterator) #114192
Comments
cc @cockroachdb/replication |
Must have called cockroach/pkg/storage/pebble_iterator.go Line 338 in f0089ab
We check that cockroach/pkg/kv/kvserver/replica_rangefeed.go Lines 394 to 396 in 9640975
However, it is set non-nil during construction and never written to anywhere else:
The test doesn't do anything with server internals to provoke this either. |
Relevant metamorphic parameters:
The full set is:
|
Of course, the iterator that was actually cockroach/pkg/storage/intent_interleaving_iter.go Line 1068 in 59d8640
|
Could be a double-close -- we cockroach/pkg/storage/intent_interleaving_iter.go Lines 1067 to 1076 in 59d8640
|
Yeah, there's a race here: cockroach/pkg/kv/kvserver/replica_rangefeed.go Lines 390 to 397 in 9640975
cockroach/pkg/kv/kvserver/replica_rangefeed.go Lines 406 to 415 in 9640975
The semantics are that cockroach/pkg/kv/kvserver/rangefeed/registry.go Lines 390 to 398 in 54b8a73
But before that returns to the caller, if the stopper fires, we return cockroach/pkg/kv/kvserver/rangefeed/scheduled_processor.go Lines 595 to 598 in ab00ae9
|
I'm going to downgrade this to a GA blocker. This only happens during node shutdown, rarely, so we don't have to hold up the beta over it. |
cc @cockroachdb/replication |
sql/flowinfra.TestEvalCtxTxnOnRemoteNodes failed with artifacts on release-23.2 @ 5c59f412f63925f930a58392d0a95980b37e0655:
Fatal error:
Stack:
Log preceding fatal error
Parameters:
TAGS=bazel,gss,deadlock
,stress=true
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-33388
The text was updated successfully, but these errors were encountered: