[SERVER-33441] ReplicaSet Issue on MongoDB Upgrade from 3.4.5 to 3.6.2 Created: 22/Feb/18 Updated: 27/Oct/23 Resolved: 05/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Replication |
| Affects Version/s: | 3.6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Manisha Pande | Assignee: | Dmitry Agranat |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
AWS |
||
| Attachments: |
|
| Participants: |
| Description |
|
We upgraded mongoDB 3.4.5 to 3.6.2 in centos, where replicaset are not syncing and connecting to each other. To resolve that we tried to resync replica configuration, but its not working. We have three mongo DB nodes. One Primary and two secondaries. Command follow to upgrade:
2. Connected to secondary mongoDB node run admin command to check version
3. Stop MongoDB in secondary Node
4. Install Mongo DB
5. Started MongoDB
6. Connected to Primary to check status of secondary run rs.status() Same issue with other secondary as well . Although they are up and running but replicas showing Connection Refused. As soon as, upgrade applied in both Secondary replicas. they automatcically they are try to become primary. Logs:
|
| Comments |
| Comment by Dmitry Agranat [ 05/Mar/18 ] | |||||||||
|
Hi mpande, Glad to hear that using the net.bindIp configuration file setting resolved the issue.
Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Thanks, | |||||||||
| Comment by Manisha Pande [ 05/Mar/18 ] | |||||||||
|
Thanks Dima. I have set net.bindIp to 0.0.0.0 in mongod.conf file in all mongodb nodes and its working, but I want to restrict to all mongo connections to nodes. I was checking custom rules for the same. could you please provide me an example of custom rules. | |||||||||
| Comment by Dmitry Agranat [ 28/Feb/18 ] | |||||||||
|
Hi mpande, Thank you for providing the requested information. From the vcp1-master-1-mongod.log I can see:
Based on our 3.6 upgrade documentation procedure, you will need to use the net.bindIp configuration file setting or the --bind_ip command-line option to specify a list of ip addresses. Please follow these steps and let us know if you still encounter this issue. Thanks, | |||||||||
| Comment by Manisha Pande [ 27/Feb/18 ] | |||||||||
|
Hi Dima, I have attached requested logs. I have provision the cluster in aws, install mongodb 3.4 version and upgraded only one mongodb node (vap1-master-1) Regards, | |||||||||
| Comment by Dmitry Agranat [ 25/Feb/18 ] | |||||||||
|
Hi mpande Thank you for the report. To get some more insight into this issue, could you please provide the following:
This should provide some information to help diagnose this. Thanks, |