[SERVER-22386] could not contact primary Created: 31/Jan/16 Updated: 06/Apr/23 Resolved: 31/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ali Hallaji | Assignee: | Stennie Steneker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
We deploy sharded cluster between multi locations(data center). I describe all details about this sharded cluster at below: Example of Error when I insert doc with shard key: ) }) My question is if bnd replica set(shard, configsvr, mongos of bnd is up) disconnected from sharded cluster, That must be work and even it insert and find, So when it connected to sharded cluster configsvr must be migrate chunk or doc from bnd replica set to thr replica set. |
| Comments |
| Comment by Ali Hallaji [ 31/Jan/16 ] |
|
Ok, Thank you very much |
| Comment by Stennie Steneker (Inactive) [ 31/Jan/16 ] |
|
Hi, The information in the current description isn't entirely clear, but this sounds like a support issue which needs some further discussion on your deployment and usage before determining if there might be a server issue. > My question is if bnd replica set(shard, configsvr, mongos of bnd is up) disconnected from sharded cluster, That must be work and even it insert and find, So when it connected to sharded cluster configsvr must be migrate chunk or doc from bnd replica set to thr replica set. If a replica set is part of a sharded cluster, you can only insert documents via a mongos. You can't isolate a replica set from a sharded cluster and expect normal operation (eg. migrations or inserting documents into an unavailable shard). The error message "could not contact primary for replica set thr" would be expected if that replica set was inaccessible or did not have a current primary. It would be more appropriate if you can start a new discussion in the mongodb-user group. MongoDB team members are active in this forum and you can also benefit from the experience of other MongoDB users. Thanks, |
| Comment by Ali Hallaji [ 31/Jan/16 ] |
|
Hi Stephen Steneker, Best Regards, |
| Comment by Stennie Steneker (Inactive) [ 31/Jan/16 ] |
|
Hi Ali, 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 our Technical Support page for additional support resources. Thanks, |