Investigate why the config.shards insert on initial sync node in config shard doesn't have commit timestamp

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • ALL
    • v8.1, v8.0
    • Hide

      See attached repro files master-repro.diff and 8.0-repro.diff and run:

      python3 buildscripts/resmoke.py run --log file --mrlog -j8 --suites=replica_sets jstests/replsets/initial_sync_succeeds_when_syncing_node_removed.js
      Show
      See attached repro files master-repro.diff and 8.0-repro.diff and run: python3 buildscripts/resmoke.py run --log file --mrlog -j8 --suites=replica_sets jstests/replsets/initial_sync_succeeds_when_syncing_node_removed.js
    • CAR Team 2024-04-15, CAR Team 2024-04-29, CAR Team 2024-05-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Adding a replica set node to a config server immediately following a topology change (such as cluster creation, adding, or removing a shard) will crash the newly added node. This is because the oplog entry reflecting the topology modification is not yet included in the stable snapshot and is subsequently replayed during recovery or initial sync.

        1. 8.0-repro.diff
          1 kB
        2. master-repro.diff
          1 kB

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

              Created:
              Updated: