[SERVER-78907] KeyManagerCache reset and then not refreshed during repl rollback Created: 12/Jul/23  Updated: 27/Oct/23  Resolved: 27/Jul/23

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

Type: Bug Priority: Major - P3
Reporter: Israel Hsu Assignee: Israel Hsu
Resolution: Gone away Votes: 0
Labels: sharding-nyc-subteam1, sharding-nyc-subteam2, sharding-nyc-tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding NYC
Operating System: ALL
Participants:

 Description   

Exposed by HELP-38218.
During replication rollback, the KeyManagerCache was reset, then not immediately refreshed before the next client operation, causing the client operation to fail with KeyNotFound.

KeyManagerCache keys will still be valid upon rollback; refresh with read-majority may not be possible while rolling back.

 


Generated at Thu Feb 08 06:39:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.