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

Fix time monotonicity violation when running shard merge suite with an auto-bootstrapped config shard.

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL

      Running any shard merge suite with auto-bootstrapping on will result in a time monotonicity violation invariant being triggered: 

      Time monotonicity violation: lookup time { topologyTime: Timestamp(1708460855, 31), rsmIncrement: 0, forceReloadIncrement: 1 } which is less than the earliest expected timeInStore { topologyTime: Timestamp(1708460865, 21), rsmIncrement: 0, forceReloadIncrement: 1 

      I think this error may somehow be caused by the ShardingReplicaSetChangeListener performing a lookup while shard merge is running.

       


       

      To reproduce the crash, checkout the following branch: 

      https://github.com/10gen/mongo/compare/wenqinYe/SERVER-83169?expand=1

      Then run the following test:

      buildscripts/resmoke.py run --suites=buildscripts/resmokeconfig/suites/shard_merge_jscore_passthrough.yml jstests/parallel/insert.js | tee test.txt

      To see the error and the backtrace, in the test.txt file search for "time monotonicty violation". 

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            wenqin.ye@mongodb.com Wenqin Ye
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: