[DOCS-8470] Explain node down & replacement design, rationale Created: 01/Aug/16  Updated: 20/Dec/18  Resolved: 20/Dec/18

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Andrew Davidson Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: groom
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 5 years, 8 weeks ago
Epic Link: DOCSP-2982
Story Points: 1

 Description   

When a node dies in MongoDB Atlas, it can take an hour before it will be automatically replaced. The UI will be updated to better explain this and a link to the documentation explaining the rationale in depth will also be available.



 Comments   
Comment by Anthony Sansone (Inactive) [ 20/Dec/18 ]

This was fixed with  this commit as part of DOCSP-1639.

Comment by Emily Hall [ 05/Aug/16 ]

Not enough information from Atlas team to groom this ticket.
Need a fixVersion and more details before planning can begin.

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