Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-89076

test_resharding_test_fixture_shutdown_retry_needed does not handle SnapshotUnavailable errors

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.9, 8.1.0-rc0, 8.0.0-rc3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.0
    • CAR Team 2024-04-15
    • 30

      The test attempts to restart nodes during a resharding operation. This can result in the following situation:

      • resharding operation chooses Timestamp T=0
      • replica set advances stable timestamp to T=1
      • secondary restarts and sets the minimum valid snapshot timestamp to be the stable timestamp
      • resharding operation attempts to scan the config.transactions table at T=0 on the secondary
      • resharding receives a SnapshotUnavailable error since the collection instances do not match because we created a new PIT collection instance.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: