Increase reshardingOplogApplierMaxLockRequestTimeoutMillis in Unit Tests

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL
    • Hide

      Setting reshardingOplogApplierMaxLockRequestTimeoutMillis to 1ms is strict enough to fail consistently on my workstation.

      Show
      Setting reshardingOplogApplierMaxLockRequestTimeoutMillis to 1ms is strict enough to fail consistently on my workstation.
    • Cluster Scalability 2024-1-22
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ReshardingOplogApplicationRules, when trying to acquire a collection, uses a deadline based on reshardingOplogApplierMaxLockRequestTimeoutMillis, which defaults to 5ms. As seen in BF-30275, this is sometimes too strict for slower variants (e.g. debug, windows). The timeout should be increased during unit tests.

            Assignee:
            Brett Nawrocki
            Reporter:
            Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: