[SERVER-33927] The NoopWriter is not resilient to `InterruptedAtShutdown` exception. Created: 16/Mar/18  Updated: 04/Sep/19  Resolved: 04/Sep/19

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Maria van Keulen
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-33674 Require GlobalLocks with deadlines to... Closed
Problem/Incident
is caused by SERVER-32638 Permit dblock acquisition waiting to ... Closed
Operating System: ALL
Sprint: Execution Team 2019-09-09
Participants:
Linked BF Score: 5

 Description   

I believe there was a recent change to make lock acquisitions with a deadline throw an InterruptedAtShutdown exception. That change broke the runtime API resulting in the NoopWriter's shutdown handling now being incomplete.



 Comments   
Comment by Maria van Keulen [ 04/Sep/19 ]

SERVER-33674 modifies the global lock acquisition in the noop writer to avoid throwing errors upon interruption. Closing this ticket as a dupe.

Comment by Maria van Keulen [ 03/Sep/19 ]

This may actually have been addressed by SERVER-33674. I will do some more investigation to confirm.

Comment by Charlie Swanson [ 19/Mar/18 ]

Looks very similar to SERVER-33785. Perhaps we should do a more thorough review of all background threads to see if others can be affected by this problem.

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