[SERVER-22904] multiple mongos are having different data Created: 01/Mar/16  Updated: 16/Nov/21  Resolved: 01/Mar/16

Status: Closed
Project: Core Server
Component/s: Sharding, WiredTiger
Affects Version/s: 3.0.6
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Rakesh Kumar Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-22905 mongos are having different data in s... Closed
Operating System: ALL
Steps To Reproduce:

In this cluster we are having multiple databases, eg. db1,db2 and db3

db1 > shard1 primary (not sharded)
db2 > shard1 primary (not sharded)
db3 > shard2 primary (not sharded)
mongos1 , mongos2, mongos3 > three mongos
 
On 10.14.4.121 (mongos1)
mongos> use admin
mongos> db.runCommand( { movePrimary: "db2", to: "shard1" } )
 
mongos> use db2
switched to db db2
mongos> db.inventories.count()
140714
mongos> ^C
 
 
On 10.14.17.245 (mongos2)
Before restart:
mongos> use db2
switched to db db2
mongos> db.inventories.count()
28
After mongos2 Restart:
mongos> use db2
switched to db db2
mongos> db.inventories.count()
140714
 
 
On 10.14.2.71 (mongos3)
Before Restart:
mongos> use db2
switched to db db2
mongos> db.inventories.count()
25
After Restart:
mongos> use db2
switched to db db2
mongos> db.inventories.count()
140714

Participants:

 Description   

Hi,

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

db1 > shard1 primary (not sharded)
db2 > shard2 primary (not sharded)
db3 > shard2 primary (not sharded)

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 Rakesh Kumar [ 01/Mar/16 ]

ticket duplicated.

Comment by Rakesh Kumar [ 01/Mar/16 ]

Please ignore and close this ticket.

Generated at Thu Feb 08 04:01:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.