[SERVER-6643] Maintenance mode should be unset when a command exits with an assertion Created: 30/Jul/12  Updated: 06/Dec/22  Resolved: 04/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-9800 Maintenance mode commands should unse... Closed
Related
related to SERVER-9338 db.runCommand( { compact: '<collectio... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Currently the server will stay in maintenance mode.



 Comments   
Comment by Spencer Brody (Inactive) [ 14/Jun/18 ]

Storage team owns the compact and repair commands

Comment by Mathias Stearn [ 30/Jul/12 ]

@Scott: correct. This only applies to commands that set maintenance mode automatically, such as compact. They are supposed to unset it when they are finished, but they only do that if they finish successfully, and not if they error out. That is what this ticket is about, not a manually triggered maintenance mode.

Comment by Scott Hernandez (Inactive) [ 30/Jul/12 ]

Wouldn't this be better as lock/lease that goes out of scope from the thing that turned it on. In maint. mode you could do something else , another client/thread, which causes an assertion but you don't want it to turn off the maint. mode, do you?

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