[SERVER-3413] moveprimary doesn't propagate changes to other mongos instances Created: 11/Jul/11 Updated: 06/Mar/13 Resolved: 17/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bryon Ross | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
After running the moveprimary command via mongos, other mongos instances that communicate with the same mongod instances may not be aware of the move. In other words, they may still send updates to the old mongod after the move is complete. Steps to reproduce:
1) Open a mongo shell to each of the two mongos instances (db=test). SHELL 1: }, SHELL 2: }, SHELL 1: ) { "primary " : "shard0001:localhost:27102", "ok" : 1 }> db.stats() }, SHELL 2: }, Note that if you restart the second mongos at this point, the document {_id:"bob", value: 2} is lost forever, as it was persisted on the wrong mongod. |
| Comments |
| Comment by James Blackburn [ 06/Mar/13 ] |
|
When was this fixed? I saw this on 2.2.1: |
| Comment by Jon Ivmark [ 19/Oct/11 ] |
|
This caused me some pain the other day (using 1.8.3). Would be really nice if it was fixed. |