[SERVER-16001] Interrupting DBDirectClient operations should be disallowed Created: 06/Nov/14  Updated: 10/Dec/14  Resolved: 14/Nov/14

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

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: J Rassi
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-14062 Remove the global OperationContext re... Closed
Related
related to SERVER-15999 checkForInterrupt() argument "heedMut... Closed
Participants:

 Description   

The introduction of rollback-enabled write operations has increased the number of DBDirectClient calls that can be interrupted (previously, DBDirectClient interruption was disabled if the caller was holding a write lock and the operation had already performed a write, see SERVER-15999), and thus increased the possibility of a bug manifesting from any users of DBDirectClient that incorrectly assumed that their DBDirectClient operations would complete successfully. As a precaution, we should disallow interruption of DBDirectClient operations entirely.



 Comments   
Comment by J Rassi [ 14/Nov/14 ]

Addressed in <https://github.com/mongodb/mongo/commit/284f942a45b877f0baecd19cbf17fc2a4e246a79>. Resolving as dup of SERVER-14062.

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