[SERVER-12178] cleanupOrphan can fail if shard is moving chunks Created: 20/Dec/13 Updated: 06/Feb/14 Resolved: 07/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Note: commit message is wrong. Forgot to change it before pushing. The fix for
Versions tested (chronological order): 6902c6b643f64 (not reproducible) |
| Comments |
| Comment by Randolph Tan [ 07/Jan/14 ] |
|
We should add in the documentation that the command can return the same start range so the client can retry if the server detected we are still transitioning the shard version. It will also print a warning: "orphaned cleanup needs to be retried, collection metadata at shard version <version> changed during reload" |
| Comment by Randolph Tan [ 07/Jan/14 ] |
|
Note: commit message is wrong. Forgot to change it before pushing. The QA script was failing because the migrate thread bump the internal major version and the chunk differ got confused when it tries to get new chunks based on the new version since it doesn't exist on the config server yet. The fix was not to fail the command, but return the same start range so the user can retry again. The command should succeed once the shard version is in steady state. |
| Comment by Githook User [ 07/Jan/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |