MongoDB.live, free & fully virtual. June 9th - 10th. Register Now MongoDB.live, free & fully virtual. June 9th - 10th. Register Now

Availability of fix for SERVER-35649

Hi Team, just wanted to know if the ticket would be available anytime in future release https://jira.mongodb.org/browse/SERVER-35649?

Hi @Joanne,

Welcome to the MongoDB Community!

Per the Jira metadata on SERVER-35649, this issue is currently Open in the Backlog and does not have a planned fixVersion yet. I suggest upvoting and watching the issue in Jira for updates.

This issue appears to affect replica set members restarted while their hostname is not resolvable via DNS. If a replica set member cannot resolve its current hostname, it will be unable to find itself in the current replica set configuration and transition to a REMOVED state.

The workaround is to restart affected replica set members after the DNS issue has been resolved.

To mitigate this issue, you could ensure the local member hostname is always resolvable via redundant DNS servers and/or add the hostname to /etc/hosts.conf.

Regards,
Stennie

Got it. Thanks for the prompt reply!

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.