[SERVER-22905] mongos are having different data in shared cluster Created: 01/Mar/16 Updated: 16/Nov/21 Resolved: 11/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rakesh Kumar | Assignee: | Kelsey Schubert |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | We have a sharded cluster of mongo 3.0.6, having 2 shards, 3 config servers and 3 mongos. In this cluster we are having multiple databases, eg. db1,db2 and db3
|
||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Hi,
After moving primary of db2 database from shard2 to shard1, after that all three mongos are showing different document counts (the one mongos from where we are running move primary command is showing right data, other two mongos are showing wrong data) |
| Comments |
| Comment by Kelsey Schubert [ 11/Mar/16 ] | ||||||||||||||||||||||||||||||||||||
|
Hi rakesh.mib.j, I'd like to summarize what we've seen:
Since neither you nor I could reproduce the behavior where after executing flushRouterConfig incorrect data was still displayed, I am going to close this ticket. If you are able reliably reproduce this issue, please comment and we will be happy to reopen this ticket and take another look. Thank you, | ||||||||||||||||||||||||||||||||||||
| Comment by Rakesh Kumar [ 08/Mar/16 ] | ||||||||||||||||||||||||||||||||||||
|
Hi Thomas, I have done testing multiple times on our staging environment, and every time we are getting 0 count result on other mongos after moving primary to different shards. Below are the test results, which are excepted: mongos1:
On Mongos2:
On Mongos3:
In prod we are having read/insert/update heavy load, but here we are testing in ideal environment. Further In Prod (where we face this issue), we found db2 exist in both shards. | ||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 03/Mar/16 ] | ||||||||||||||||||||||||||||||||||||
|
Hi rakesh.mib.j, To continue to investigate this behavior we will need some more information. Are you able to reproduce this issue? If so, can you please
After reproducing the issue, including the new steps I have listed above, we will want the following:
Thank you for your help, | ||||||||||||||||||||||||||||||||||||
| Comment by Rakesh Kumar [ 01/Mar/16 ] | ||||||||||||||||||||||||||||||||||||
|
FYI : We are having sharded cluster, but we haven't shard any database. |