Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-14674

Shard dies during chunk migration if running repairDatabase and Compact

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • 2.6.1
    • None
    • Sharding
    • ALL
    • Hide

      Not sure if this is 100% reproducable

      Show
      Not sure if this is 100% reproducable
    • Sharding 2019-02-25

    Description

      Shard dies with a stack trace pointing to DummyRunner class destructor.
      During chunk migration, if running repairDatabase and compact, it will cause the old collection pointer to be invalid. You will get a different pointer when you call the getCollection method. The current workaround for this is to stop the balancer whenever user runs these commands.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-15647 Extent Manager must be Thread-safe

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

          Task - A task that needs to be done. SERVER-15633 ShardingState::doRefreshMetadata should take a more granular lock than exclusive db

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

          Activity

            People

              kaloian.manassiev@mongodb.com Kaloian Manassiev
              alex.lerner Alex Lerner
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: