If the orphans check runs concurrently with the drop, finds an entry in config.collections here, but later it queries config.collections again as part of findChunksUtil.findChunksByNs (to decide whether to join the config.chunks by 'ns' or 'uuid'), but now the collection entry has already been deleted by the drop, so it fails.
Orphans check at the end of jstest can fail in presence of concurrent drop collection
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: