[DOCS-11291] Document the Atlas cluster upgrade process Created: 06/Feb/18  Updated: 29/Oct/23  Resolved: 09/Apr/18

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

Type: Improvement Priority: Major - P3
Reporter: Angela Morgan (Inactive) Assignee: Robert Justice (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 5 years, 44 weeks, 2 days ago
Epic Link: DOCSP-1743
Story Points: 0.5

 Description   

A customer had the following questions about the upgrade process:

"Besides not being able to downgrade to 3.4 again, what other consequences are there?
Will old backups not work anymore?
How long does the upgrade take?
Will the cluster be offline during upgrade?
Other things I should be aware of?"

Thanks,
Angela.

2/7/2018 Docs Triage Notes:

Suggested Action Items:

  • Emphasize the backup/restoration compatibility and snapshot restore restrictions on the following pages:
  • Confirm above bullet with engineering


 Comments   
Comment by Robert Justice (Inactive) [ 09/Apr/18 ]

Ravind merged!

Comment by Ravind Kumar (Inactive) [ 07/Feb/18 ]

Via MMS ticket:

  • Will old backups not work anymore?

Yes, you can still restore from a 3.4 backup. You will need to restore a 3.4 backup to a 3.4 cluster then upgrade that cluster to version 3.6.

  • How long does the upgrade take?

There is no fixed length of time because it will depend on factors such as the number of nodes that need to be upgraded.

  • Will the cluster be offline during upgrade?

Atlas always upgrades the cluster using a rolling process to maintain cluster availability.
Please let me know if you have questions on any of the above.

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