Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
6.5.0
-
Triaged
-
Unknown
Description
If we disconnect we may receive two commits/aborts (or some combination of the two) in a row. Currently for EP Buckets this would cause an exception to throw and the DCP connection to be torn down as we would not find the existing prepare in the hash table to set the prepared seqno of the commit/abort. We need to be resilient to this and allow multiple commits/aborts. We only wish to allow this for the specific disconnect/reconnect case though. Believe it's enough to make a check such that if we receive a commit/abort with current highSeqno < seqno < streamStart then we should allow the "duplicate".