[SERVER-43405] Do not acquire the RSTL for idents cleanup Created: 20/Sep/19  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Storage Execution
Participants:
Linked BF Score: 17

 Description   

Currently, dropIdentsOlderThan acquires a global intent lock, which then implicitly acquires RSTL. Slowness in the subsequent for loop of dropping idents could result in delay in replication state transitions because TimestampMonitor is not killable by the RstlKillOpThread. This ticket is to investigate whether idents cleanup needs synchronization with step up and step down. If not, consider dropping RSTL for idents clean.


Generated at Thu Feb 08 05:03:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.