[SERVER-12805] Admin check for sharding Created: 20/Feb/14  Updated: 03/Dec/16  Resolved: 03/Dec/16

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

Type: Improvement Priority: Major - P3
Reporter: Charlie Page Assignee: Daniel Pasette (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

One of the large problems people with large shard deployments have is determining if all of the mongoS have been upgraded (they seem to forget about that application server deployed a year ago in some corner). There have been various customers where we find that they are running older mongoS in their clusters and didn't know it.

As part of the admin tools which check upgrades that mattd@10gen.com is working on, it would be great if those tools could also check shards, both before upgrading and after an upgrade is believed to be complete (or every step along the way). That way we have run this tool instead of: check these 5 things with these 5 steps.

The one test that I can think of immediately is getting all of the mongoS versions and assuring they have all been upgraded.



 Comments   
Comment by Daniel Pasette (Inactive) [ 03/Dec/16 ]

The upgrade process has evolved since this ticket was filed and it is no longer relevant.

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