[SERVER-33599] Out collection not in UUID catalog when shards started as replica sets in mapReduce_outSharded.js, mrShardedOutput.js, forget_mr_temp_ns.js Created: 01/Mar/18  Updated: 15/May/18  Resolved: 15/May/18

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

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-33538 mapReduce "replace" on a sharded outp... Closed
Related
is related to SERVER-32052 Update ShardingTest to default to sta... Closed
Sprint: Sharding 2018-05-21
Participants:

 Description   

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.



 Comments   
Comment by Janna Golden [ 15/May/18 ]

The error that occurs in these tests is the same error that SERVER-33538 describes.

Generated at Thu Feb 08 04:33:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.