[SERVER-5862] moveChunk fails with "couldn't find chunk" after moving from one shard to another repeatedly Created: 17/May/12  Updated: 14/Apr/16  Resolved: 05/Jun/15

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File move_chunk.js    
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Initialization: chunkA is owned by shard1

Steps to reproduce:

1. Move chunkA to shard2.
2. Move chunkA back to shard1
3. Keep on repeating steps 1 and 2 until it fails.



 Comments   
Comment by Greg Studer [ 06/Mar/14 ]

renctan Expect this is now fixed with our more deterministic reload logic before every metadata command.

Comment by Randolph Tan [ 17/May/12 ]

Attached test case. Always fails at 2nd round.

Generated at Thu Feb 08 03:10:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.