[SERVER-17474] Mongos doesn't see new sharded collection Created: 05/Mar/15 Updated: 06/Dec/22 Resolved: 07/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Migalin Danila | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
I have sharded cluster and several mongos instances connected to it. After that, half of mongos instances began to see whole collection as sharded, but some mongos still thinks, than collection is not sharded and is empty. Examples:
'bad' mongos:
After 'bad' mongos restart, everything becomes OK. |
| Comments |
| Comment by Kaloian Manassiev [ 07/Mar/19 ] | |||||||
|
With the changes done in 3.2 to make all CRUD operations attach shard version instead of going through ShardConnection and with the changes in 4.0.6 to make shards drive the collection sharding process, this should no longer be an issue. | |||||||
| Comment by Migalin Danila [ 05/Mar/15 ] | |||||||
|
flushRouterConfig helps:
| |||||||
| Comment by Randolph Tan [ 05/Mar/15 ] | |||||||
|
Next time this happens again, try calling the { flushRouterConfig: 1 } before restarting. | |||||||
| Comment by Daniel Pasette (Inactive) [ 05/Mar/15 ] | |||||||
|
Hi Migalin, "last commenter" in this case only means that the fixVersion was flipped to "debugging with submitter" | |||||||
| Comment by Migalin Danila [ 05/Mar/15 ] | |||||||
|
Uhh, sorry, I see at ticket's header
But doesn't see any comment, looks like I doesn't have an access to them |