[SERVER-40822] MongoDB Replica set is not joining after changing the containers in Docker. Created: 24/Apr/19 Updated: 30/Apr/19 Resolved: 30/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | harshavardhan | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Docker container |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
2019-04-24T09:51:43.453-0500 I REPL [initandlisten] Recovering from stable timestamp: Timestamp(1556117443, 1) (top of oplog: { ts: Timestamp(1556117485, 1), t: 43 }, appliedThrough: { ts: Timestamp(0, 0), t: -1 }, TruncateAfter: Timestamp(0, 0)) |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 30/Apr/19 ] | |||
|
That indicates to me that the container was then able to satisfy name resolution which allowed the node to be recognized as a member of the replica set. The SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. | |||
| Comment by harshavardhan [ 29/Apr/19 ] | |||
|
No, we are not seeing any error message after running rs.reconfig(). | |||
| Comment by Danny Hatcher (Inactive) [ 29/Apr/19 ] | |||
|
The name resolution failure can be temporary; MongoDB will try to resolve to the hostname and it appears that it succeeded. Are you still seeing the warning messages in the logs?
| |||
| Comment by harshavardhan [ 29/Apr/19 ] | |||
|
If this is caused by DNS issue. why is it resolved after I ran rs.reconfig() without restarting the container? Can I get any help here?
| |||
| Comment by Danny Hatcher (Inactive) [ 29/Apr/19 ] | |||
|
This appears to be an issue with the DNS which causes MongoDB to not associate the hostname with a member in the replica set config:
If you restart the container, does the "Temporary failure in name resolution" error happen again? If so, you need to investigate the deeper DNS issues which is outside the scope of MongoDB. |