Upate sharding write router benchmark to handle LocalReshardingOperationsRegistry

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The sharding write router benchmark is currently failing internal assertions silently since benchmarks aren't marked as failed for this type of failure. It looks like this benchmark was working in 8.3 but since the changes to the LocalReshardingOperationsRegistry is no longer passing its assertions.

            Assignee:
            Unassigned
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: