j***@gmail.com
2017-03-10 03:50:56 UTC
Hello,
Presently running a production replica set (3 member + 1 hidden) on 3.0.9.
Looking to upgrade to the latest version and have been testing the process
I've used since 2.4, which is as follows:
1) Create a copy of existing replica set running the updated version of
mongo and add to replica set
2) Alter the replica set config to swap priorities over to the new servers,
electing a new primary.
3) Alter the replica set config to remove the old servers.
I've performed this process with 3.0.9 to 3.2 in testing with a replica of
my production environment and it seemed to go reasonably well however,
there was some behaviours I have not encountered previously.
Some of the new secondaries once added in were ok initially via rs.status()
but eventually failed to find a member to sync from. Returning; "lastHeartbeatMessage"
: "could not find member to sync from".
I had to manually specify on each node using rs.syncFrom().
Once I got through adjusting the replica set config switching to the new
3.2 servers, they seemed to start syncing fine but I reverted back and
tried a few more times with the same situation.
Have not experienced that ever before previously, and wondering what the
reason might be?
Have tried going through the docs and changelogs but can't find any hint
that rolling upgrade between 3.0.x and 3.2+ is no longer a supported
method. Also could not find anything helpful in the logs regarding the
failure to sync.
Can anyone advise on what might be going on here? Along with the best
practice for performing a minimal downtime rolling upgrade to get from
3.0.9 to latest?
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/3178a6cf-c9fa-49f6-be8e-41b089f390b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Presently running a production replica set (3 member + 1 hidden) on 3.0.9.
Looking to upgrade to the latest version and have been testing the process
I've used since 2.4, which is as follows:
1) Create a copy of existing replica set running the updated version of
mongo and add to replica set
2) Alter the replica set config to swap priorities over to the new servers,
electing a new primary.
3) Alter the replica set config to remove the old servers.
I've performed this process with 3.0.9 to 3.2 in testing with a replica of
my production environment and it seemed to go reasonably well however,
there was some behaviours I have not encountered previously.
Some of the new secondaries once added in were ok initially via rs.status()
but eventually failed to find a member to sync from. Returning; "lastHeartbeatMessage"
: "could not find member to sync from".
I had to manually specify on each node using rs.syncFrom().
Once I got through adjusting the replica set config switching to the new
3.2 servers, they seemed to start syncing fine but I reverted back and
tried a few more times with the same situation.
Have not experienced that ever before previously, and wondering what the
reason might be?
Have tried going through the docs and changelogs but can't find any hint
that rolling upgrade between 3.0.x and 3.2+ is no longer a supported
method. Also could not find anything helpful in the logs regarding the
failure to sync.
Can anyone advise on what might be going on here? Along with the best
practice for performing a minimal downtime rolling upgrade to get from
3.0.9 to latest?
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/3178a6cf-c9fa-49f6-be8e-41b089f390b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.