-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16
-
0
Besides the issues with the workload in the stepdown suites outlined in SERVER-25534, the database_versioning.js workload is failing with a WriteConflict error in the non-stepdown suites:
[fsm_workload_test:database_versioning] 2018-06-11T19:24:39.214+0000 Foreground jstests/concurrency/fsm_workloads/database_versioning.js [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.214+0000 Error: command failed: { [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.215+0000 "ok" : 0, [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.215+0000 "errmsg" : "WriteConflict", [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.215+0000 "code" : 112, [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.215+0000 "codeName" : "WriteConflict", [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 } [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 } [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 _getErrorWithCode@src/mongo/shell/utils.js:25:13 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 quietlyDoAssert@jstests/concurrency/fsm_libs/assert.js:55:18 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 _assertCommandWorked@src/mongo/shell/assert.js:534:17 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 assert.commandWorked@src/mongo/shell/assert.js:618:16 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 wrapAssertFn@jstests/concurrency/fsm_libs/assert.js:67:13 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.216+0000 assertWithLevel/</assertWithLevel[fn]@jstests/concurrency/fsm_libs/assert.js:106:13 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.217+0000 movePrimary@jstests/concurrency/fsm_workloads/database_versioning.js:71:13 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.217+0000 state@jstests/concurrency/fsm_workloads/database_versioning.js:87:21 [fsm_workload_test:database_versioning] 2018-06-11T19:24:39.217+0000 runFSM@jstests/concurrency/fsm_libs/fsm.js:46:13...
This ticket is to investigate the failure further and either unblacklist the test by fixing the server bug if that's what's causing it or updating the test to tolerate the error.
- is related to
-
SERVER-34072 config.databases writes with new version field should take the global IX lock rather than the fcvLock
- Closed
- related to
-
SERVER-44240 Remove TODO listed in SERVER-35538
- Closed