-
Type: Bug
-
Resolution: Unresolved
-
Priority: 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".