Uploaded image for project: 'Core Server'
  1. Core Server
  2. 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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Sprint:
      Sharding 2018-05-21

      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.

        Attachments

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33538 mapReduce "replace" on a sharded output collection can lead to UUIDCatalog inconsistencies

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-32052 Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              janna.golden Janna Golden
              Reporter:
              janna.golden Janna Golden
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: