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

Account for one more chunk in shard_existing_coll_chunk_count.js (v4.4)

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.15
    • Affects Version/s: 4.4.14
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-06-13
    • 20

      According to the logs of a failure, a refresh from a stale CSRS node did not allow the shard to acknowledge 2 splits. As a result, the shard auto-splitted more than needed.

      Make this check more loose, allowing the presence of an additional chunk.

      The failure has only been observed on v4.4 branch, probably because in v5.0 the commit of the chunk split happens with majority, while in v4.4 the default write concern was 1.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: