-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
When an async delete starts, it's possible that the collection and shard key index it expects could have disappeared. This isn't actually an invariant, and should be expected.
http://buildlogs.mongodb.org/Linux%2032-bit%20debug/builds/2271/test/sharding/prefix_shard_key.js
- duplicates
-
SERVER-7998 sharding/remove2.js failure in buildbot
- Closed
- is related to
-
SERVER-7376 migrate deletion not aggressive enough and tied to migrate moves
- Closed