ubuntu - Upgrading Mongodb when config instances use the same binary as data instances -


i'm upgrade sharded mongodb environment 2.0.7 2.2.9, want upgrade 2.4.9 apparently need via 2.2. release notes 2.2 state config servers should have binaries upgraded first, shards. have config instances using same mongo binary data instances. there 3 shards each 3 replicas, , 1 replica out of each shard functions config instance. since share binary can't upgrade config instances independent of of data instances.

  1. would upgrading data instances before of config instances cause problems, assuming i've disabled balancer?
  2. should change config instances use different copy of binary? if so, what's best way go existing production setup running on ubuntu 12?
  3. should remove 3 data instances replica sets, upgrade config instances, start data instances again, updating them well, in right order? last option bit hairy primaries, have step them down before removing them replica sets. last option occur again when have next upgrade, i'm not fan.

i resolved issue by:

  1. adding binaries new version new folder.
  2. restarting config instances using new binaries data instances continue run old binaries
  3. once of config servers upgraded created yet folder in put same new binaries step 1
  4. i restarted data instances using these new binaries
  5. now config instances , data instances on same server using new binaries in different folders easier upgrade them next release

note there other steps involved upgrade, , these specified in release notes should follow. however, how dealt shared binary problem not directly addressed in release notes.

a lot of tutorials seem use single binary data , config instances on single server problematic when it's time upgrade. i'd suggest using separate binaries config , data instances.


Comments

Popular posts from this blog

PHPMotion implementation - URL based videos (Hosted on separate location) -

javascript - Using Windows Media Player as video fallback for video tag -

c# - Unity IoC Lifetime per HttpRequest for UserStore -