Details
Description
Since it was observed that preCheckCasCheck takes around 11 seconds, blocking the pipeline creation + start, it has been disabled by default in MB-63005. To enable it back some work needs to be done to reduce this overhead. Some work I can think of that can to be done:
1. Follow-up on kv_engine to implement MB-62956 and use the new implemented API.
2. Concurrently execute preCheckCasCheck with some other part of pipeline start (with VBMasterCheck?)
3. Optional - We can look into if we really need max_cas getter in bucket topology service given we only use it when a new pipeline is created. (Or if a standalone call everytime a new pipeline is created will suffice)
Attachments
Issue Links
- causes
-
MB-63010 [BP 7.6.3] - XDCR - Disable new pipeline cas poisoning check
- Resolved
-
MB-63009 [BP 7.2.6] - XDCR - Disable new pipeline cas poisoning check
- Closed
- depends on
-
MB-62956 Create a new stat or a bespoke API to retrieve max_cas information
- Open
- finishs with
-
MB-63005 XDCR - Disable new pipeline cas poisoning check
- Resolved