[DOCS-13354] Investigate changes in SERVER-43988: shutdown ({force:false}) should refuse to shut down if there is an index build in progress Created: 21/Jan/20  Updated: 13/Nov/23  Resolved: 06/May/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-43988 shutdown ({force:false}) should refus... Closed
Duplicate
Participants:
Days since reply: 3 years, 40 weeks ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

Reduces the likelihood of losing progress in long running index builds for Cloud with optional restarts.
Shutdown command is now dependent on current state of index builds (in addition to replication lag as currently documented)

Description of Linked Ticket

If a user attempts to shut down the server using the shutdown command without the force: true option while there is an index build in progress, we should reject the shutdown request. This reduces the possibility of losing any progress we have made, especially with long running index builds.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 06/May/20 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}

Message: DOCS-13354: Shutdown blocks on in-progress index builds
Branch: master
https://github.com/mongodb/docs/commit/b5bc292e486e76f0da10b7e9f00b831b224f1450

Comment by Ravind Kumar (Inactive) [ 23/Mar/20 ]

Work for this ticket is being handled as part of the simultaneous index builds docs.

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