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

Shutdown during move chunk commit fasserts

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.3.12
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2016-10-10

    Description

      There are certain cases where the state after a commit chunk operation is not known and the shard needs to do a majority write in order to obtain the latest config server optime. This particular write is not allowed to fail, because the shard's cached metadata and config server op time cannot be trusted.

      In the case where a shutdown happens at the exact time of chunk commit the shard will not continue serving requests and therefore we should special case this and not fassert.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: