[SERVER-35538] unblacklist database_versioning.js workload from non-stepdown concurrency suites Created: 11/Jun/18  Updated: 01/May/20  Resolved: 24/Oct/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Won't Fix Votes: 0
Labels: open_todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-44240 Remove TODO listed in SERVER-35538 Closed
is related to SERVER-34072 config.databases writes with new vers... Closed
Sprint: Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16
Participants:
Linked BF Score: 0

 Description   

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.

 

 

 


Generated at Thu Feb 08 04:40:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.