I've been upgrading my repl set the last couple days; the plan is to spawn new 3.0 instances (we were on 2.6.5) -- let them sync to a secondary, and then start taking the older nodes out.
Now, I have one 2.6.5 instance left, and I'm spawning a 3.0 AMI image that is ready to go, but the last two times I have tried:
> rs.add('new-instance-addr')
...when I run rs.status() it indicates the new instance which is in state STARTUP2 is syncing to the PRIMARY? The first time it happened, I did not catch it but it did not end well for our production deployment until I pre-maturely killed the instance that was syncing to the PRIMARY. Tonight I spawned a new instance, and immediately checked it and it again chose to sync from the PRIMARY, so I killed it.
AFAICT there's no way to indicate a sync preference when you add a member to a replica set. But I cannot have a new member sync off the PRIMARY.
What am I missing? Prior to this, I spawned a number of servers and added them to the repl set and they all synced off one of the secondaries.
Thanks in advance