Fix race condition in ReshardingOplogFetcherTest

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ClusterScalability Jun9-Jun23, ClusterScalability Jul7-Jul20, ClusterScalability Jul21-Aug3
    • 200
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In ReshardingOplogFetcherTest for some reason sometimes a ReshardingOplogFetcher is accessed after the test is finished.

      This is hard to reproduce. I was able to reproduce it around 10% of the times, but only when:
      1. Compiling with --config=dbg_aubsan
      2. Running `stress -c <number of CPUs>` in parallel with the test.

      This looks like a purely testing problem.

      Stack trace and logs are attached

        1. address_sanitizer_error.txt
          47 kB
        2. logs.txt
          919 kB

              Assignee:
              Kruti Shah
              Reporter:
              Ivan Fefer
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: