Fix change_streams_split_event_v1_v2_tokens.js reshardCollection's initial chunk split (v8.0)

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.5, 7.0.17
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0
    • Cluster Scalability 2024-12-23
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      change_streams_split_event_v1_v2_tokens.js reshards a collection without specifying numInitialChunks. This causes the server to use sampling-based split policy, but there are not enough documents to generate the requisite number of chunks.

      The fix is to specify the intended numInitialChunks in the reshardCollection command so that it does not use sampling-based split policy.

      It looks like this test no longer exists in the master branch. The fix is for backports in the inidicated branches below.

            Assignee:
            Israel Hsu (Inactive)
            Reporter:
            Israel Hsu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: