[SERVER-4993] split command issued from shell should be more robust Created: 16/Feb/12 Updated: 11/Jul/16 Resolved: 06/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Shell |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
In general, it would be nice if the "split" (and also the "moveChunk") command, when issued with a "middle" or "find" parameter (so not specifying exact chunk bounds) would recover and retry instead of throwing an error if the shard version is stale at that point (b/c of an autosplit, for example). This is generally helpful, but mostly for tests, where autosplitting can get triggered semi-randomly and makes tests using split / moveChunk much harder to design. |
| Comments |
| Comment by Greg Studer [ 06/Mar/14 ] |
|
Fixed by metadata reload before all split operations in mongos. |