You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When batches are split downstream of the transaction pipeline
interceptor, they must unset AsyncConsensus to avoid cases where a read
misses an un-validated, pipelined write that failed.
Note that we don't do this when splitting requests _by range_, because
those splits won't separate a scan from an overlapping write.
This should be very rare since it requires a read/write batch that SQL
doesn't typically produce and both reads must be be locking requests so
that CanPipeline returns true for all requests in the batch. It seems
unlikely that such a batch is ever produced outside in the standard
configuration outside of KVNemesis.
Fixes#150304
Release note: None
0 commit comments