[v8.0 staging] Make transactions_targeting_errors.js robust against StaleConfig errors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.3, 8.0.17
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability Oct27-Nov10
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Starting in 8.0, the filtering metadata refresh during shardCollection is performed outside the critical section in a best effort way to avoid holding the critical section while talking to the config server. Therefore, it is possible for the filtering metadata to still be unknown when the transaction below starts. Given this, perform a find to trigger a filtering metadata refresh to prevent the transaction from hitting a StaleConfig error.

      Please note that this test has been removed from 8.1+ by SERVER-68131.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: