[SERVER-26546] Use unsharded collections in mongodb shard Created: 10/Oct/16 Updated: 06/Jan/17 Resolved: 06/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | hunter | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
We use the mongodb shard cluster, event collections use unsharded. But now the event collections in multiple nodes, why the number of nodes, not only in the primary shard mongos: { "_id" : "event", "primary" : "node02", "partitioned" : false }node01:PRIMARY> show dbs; node02:PRIMARY> show dbs; |
| Comments |
| Comment by Kelsey Schubert [ 06/Jan/17 ] | ||||||
|
Hi poorgreatly, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. Unfortunately, without additional information about how to reproduce this behavior, it's very challenging to understand what occurred. If you are able to reproduce this issue or encounter it again and can provide additional details about the circumstances that cause this issue, we will reopen this ticket and continue to investigate. Kind regards, | ||||||
| Comment by Kelsey Schubert [ 02/Dec/16 ] | ||||||
|
Hi poorgreatly, Sorry for the delay getting back to you. Unfortunately, we have not been able to identify the cause of this behavior. Is this still an issue for you? Have you observed this issue since then? Thank you, | ||||||
| Comment by hunter [ 12/Oct/16 ] | ||||||
|
hi Thomas Schubert, Sorry, forgot to tell you to set shard, after 10 | ||||||
| Comment by hunter [ 12/Oct/16 ] | ||||||
|
hi Thomas Schubert, | ||||||
| Comment by hunter [ 12/Oct/16 ] | ||||||
|
hi Thomas Schubert, | ||||||
| Comment by hunter [ 12/Oct/16 ] | ||||||
|
hi Thomas Schubert, | ||||||
| Comment by Kelsey Schubert [ 12/Oct/16 ] | ||||||
|
Hi poorgreatly, Thank you for providing the logs. I see the following log messages mongos_01:
This indicates that the collections in the event database are sharded. Would you please investigate whether this command explains the behavior that you observe? Thank you, | ||||||
| Comment by hunter [ 12/Oct/16 ] | ||||||
|
hi Thomas Schubert, | ||||||
| Comment by Kelsey Schubert [ 12/Oct/16 ] | ||||||
|
Hi poorgreatly, Thanks for clarifying that you haven't executed movePrimary. So we can get a better idea of what is going on here, would you please provide the logs that I requested?
I've created a secure upload portal for you to use. Files uploaded to this portal are only visible to MongoDB employees investigating this issue and are routinely deleted after some time. Thanks again, | ||||||
| Comment by hunter [ 12/Oct/16 ] | ||||||
|
hi Thomas Schubert, | ||||||
| Comment by Kelsey Schubert [ 11/Oct/16 ] | ||||||
|
Hi poorgreatly, Thank you for reporting this behavior. Have you executed movePrimary against this database? If so, would you please outline the steps you took? To help us continue to investigate, would you please provide the complete logs of a mongos, the primary config server, and the primary of each shard? Kind regards, | ||||||
| Comment by hunter [ 11/Oct/16 ] | ||||||
|
3.2.9 also have this problem |