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

Make analyze_shard_key.js workload more robust

    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v8.0, v7.3, v7.0
    • 200

      To solve BF-33850, we should skip the monotonicity check if the percentage of shard key updates is high since they overwrite the recordId order in the shard key index.

      To solve BF-30851, we should skip the size of length of "mostCommonValues", if the workload is running in a suite that performs unclean shutdown since it causes collStats to return wrong number of docs (or even that the collection is empty) and cardinality and frequency calculation for unique shard key depends on the metrics returned by collStats.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: