0

I am trying to update my mongo sharded version from 2.4 to 2.6.3.

I have some queries on steps to update this.

  1. When I will run one mongos with the --upgrade option, will it update all the config and mongos or do I have to manually replace binaries on each one of them and restart the mongos and config?
  2. How can I update my config servers without downtime?
  3. Upgrading shard needs to down its members one by one and update the binary. Is there any other way to do it?
0

All details are here: http://docs.mongodb.org/manual/release-notes/2.6-upgrade/

Answer 1: All metadata will get updated. I suggest to execute the mongos --upgrade using an extra mongos

Answer 2: You don't have any downtime from the config servers since mongos have the require cached information and balancer is disable

Answer 3: There is no other way. You upgrade the secondaries and then promote one of them to PRIMARY and upgrade the old-PRIMARY. Downtime is minimal (1-2 second my case) if replica set are well-sync

  • Hi Antonis i have one question for config servers if i bring down them one by one to replace the binary it will not make any impact on sharded cluster. Like if that time my application is writing data in collections which are sharded. – viren Aug 4 '14 at 16:27
  • Mongos keep a cached copy of your cluster structure (same a config servers). In case all your config servers goes down and you didn't restart the mongos your cluster will be operational but no split/migrations can be happened. – Antonios Aug 4 '14 at 16:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.