-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
roachtest: version/mixed/nodes=5 failed #38996
Comments
We see a
This must have been broken by #38817. It almost certainly has to do with the nullability of |
Oh, this is after a snapshot. We see that the on-disk state of the |
We can't strip the key out of the kv batch we send in snapshots because then the follower would become inconsistent and would fail consistency checks. Instead, we need to continue sending this key in the |
Fixes cockroachdb#38996. We saw in the referenced issue that a 19.1 node crashed after being sent a snapshot with a TxnSpanGCThresholdKey but without the corresponding value in SnapshotRequest_Header.ReplicaState.TxnSpanGCThreshold. This commit avoids this assertion failure by continuing to send this field in the snapshot header, even though it is no longer maintained. 19.2 nodes will ignore the field during entry application and during snapshot ingestion, so the change has no effect on them. However, we can rest assured that the same assertion would fire if we messed this up on 19.2 nodes. Release note: None
39003: storage: continue sending ReplicaState.TxnSpanGCThreshold to 19.1 nodes r=ajwerner a=nvanbenschoten Fixes #38996. We saw in the referenced issue that a 19.1 node crashed after being sent a snapshot with a TxnSpanGCThresholdKey but without the corresponding value in SnapshotRequest_Header.ReplicaState.TxnSpanGCThreshold. This commit avoids this assertion failure by continuing to send this field in the snapshot header, even though it is no longer maintained. 19.2 nodes will ignore the field during entry application and during snapshot ingestion, so the change has no effect on them. However, we can rest assured that the same assertion would fire if we messed this up on 19.2 nodes. Release note: None Co-authored-by: Nathan VanBenschoten <[email protected]>
SHA: https://github.com/cockroachdb/cockroach/commits/1ca35fc4a0e2665e7f6efd945e65a0db97984fa7
Parameters:
To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1396096&tab=buildLog
The text was updated successfully, but these errors were encountered: