[SERVER-69617] MongoServerError: Could not find host matching read preference { mode: "primary" } for set ShardReplSet2 Created: 13/Sep/22 Updated: 05/Dec/22 Resolved: 13/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | joseph madanu | Assignee: | Backlog - Triage Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Triage
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi Guys This is the issue i am facing if any one knows please help me MongoServerError: Could not find host matching read preference { mode: "primary" } for set ShardReplSet2 |
| Comments |
| Comment by Chris Kelly [ 13/Oct/22 ] |
|
We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |
| Comment by Chris Kelly [ 13/Sep/22 ] |
|
Hi Joseph, In order to investigate this further, we require more context. For each node in the replica set spanning a time period that includes the incident, would you please archive (tar or zip) and upload to the ticket:
Can you describe what you were trying to do leading up to the problem? It sounds like you were trying to create a sharded cluster. This is most likely a configuration issue of some sort, so I also encourage you in the check out the MongoDB Developer Community Forums for similar reports of this issue (there's quite a few). Regards,
|