top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Upgrade from MongoDB 2.6.8 to upgrade to 3.2.

+1 vote
402 views

I have a MongoDB 2.6.8 and want to upgrade to 3.2.Sharding is currently running and needs to upgrade with low downtime (Ill be happy if I get Zero downtime)
Please share best standard process/documentation/checklist?

posted Feb 24, 2017 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

First upgrade to 3.0 from 2.6 and then from 3.0 to 3.2.

Follow the documentation of 3.2 upgrade -
https://docs.mongodb.com/manual/release-notes/3.2-upgrade/

answer Feb 24, 2017 by Salil Agrawal
Similar Questions
+1 vote
Upgrade of GIT from 1.8.4 to 2.0.3

I have an issue to update the git on Mac. I am trying to use this command line to update my git to 2.0.3. 

git clone https://github.com/git/git

I currently have git 1.8.4, and I have no idea to remove the older version either. Please help me.

+1 vote
Connecting to MongoDB 2.6.12 using Java Driver version 0.11?

Can we connect to MongoDB Server 2.6.12 using Java Driver version 0.11? We have a constraint of upgrading Java Driver version which would require huge change in our client code. We use JDK 8 for compilation of our project. We would like to know whether it is possible to connect to MongoDB Server 2.6.12 or MongoDB Server 3.0 using Java Driver version 0.11 if we only use the limited set of features (not the functionalities that were introduced in Server version 2.6.12 or 3.0).

+2 votes
Write concern in mongodb 2.6

I have a 2 node replication, and in the client, set :w => 2. After the write operation, could the data be get from read-only node immediately? The document of write concern, not mention the data state in read-only node of replication. The data could be in WAL, and not visible to clients.

+1 vote
"explain" with the new PHP driver and MongoDB 3.2?

I recently upgraded the latest PHP driver and could do an "explain" query by using the "$explain" modifier when executing the query, however as of MongoDB 3.2 the operator was removed so this is no longer possible.

So my question is how can I do an explain query with the new driver and MongoDB 3.2?

...