config_shard_catalog_cache_refresh.js: wait for threads in a more reliable way

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-11-11
    • 0
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      config_shard_catalog_cache_refresh.js needs to wait for six hits of a failpoint. Instead of using the hitcount of the failpoint, it relies on getLog to count the number of occurrences of the log line that informs that the failpoint was hit. This is unreliable, because getLog only returns the last 1024 log lines, so if more than 1024 lines are produced between the first and last message, the assert.soon condition will never be met.

      This ticket should revisit why the hitcount of the failpoint can't be used for its intended purpose.

            Assignee:
            Aitor Esteve Alvarado
            Reporter:
            Aitor Esteve Alvarado
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: