Details
-
Bug
-
Resolution: Fixed
-
Critical
-
6.5.0
-
Triaged
-
No
-
KV-Engine MH Beta part 2
Description
We need to seqno ack when we create a new passive stream (or reconnect) for non-empty vBuckets to ensure that the active node can commit (may have an infinite timeout SyncWrite due to warmup or promotion so we could otherwise block a key forever).
Attachments
Issue Links
- causes
-
MB-35441 TSan: lock-order-inversion between PassiveDM::state lock & StreamMutex
- Closed
For Gerrit Dashboard: MB-35361 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
112781,6 | MB-35361: Send seqno ack on stream (re)connection | master | kv_engine | Status: MERGED | +2 | +1 |
112908,4 | MB-35441 [SR]: Fix lock-order-inversion in PassiveStream::acceptStream | master | kv_engine | Status: MERGED | +2 | +1 |