-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding 2018-05-21
If shards are started as replica sets in mapReduce_outSharded.js, mrShardedOutput.js, or forget_mr_temp_ns.js the tests seg fault when checking UUIDs during shutdown. The seg fault happens in UUIDCatalogObserver::onCollMod because the out collection doesn't exist in the UUID catalog.
- duplicates
-
SERVER-33538 mapReduce "replace" on a sharded output collection can lead to UUIDCatalog inconsistencies
- Closed
- is related to
-
SERVER-32052 Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones
- Closed