[SERVER-31452] Run fuzzer with shard stepdowns Created: 06/Oct/17  Updated: 30/Oct/23  Resolved: 19/Jan/18

Status: Closed
Project: Core Server
Component/s: Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.4, 3.7.2

Type: Task Priority: Major - P3
Reporter: Ian Boros Assignee: Kevin Albertson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-30979 Run the fuzzer with CSRS primary step... Closed
Duplicate
is duplicated by SERVER-24327 Run stepdowns in parallel with other ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: TIG 2018-1-15, TIG 2018-1-1, TIG 2018-1-29
Participants:

 Description   

SERVER-30979 will probably be committed with just config stepdowns, so as a separate task, the fuzzer should also run with shard stepdowns.



 Comments   
Comment by Githook User [ 10/Mar/18 ]

Author:

{'email': 'kevin.albertson@10gen.com', 'name': 'Kevin Albertson', 'username': 'kevinAlbs'}

Message: SERVER-31452 run fuzzer with shard stepdowns

(cherry picked from commit e0febf2c258d77a179bdcf12ef8318ea92d12ee0)
Branch: v3.6
https://github.com/mongodb/mongo/commit/79772b87467e872cbb7e8e152804014f8d9c74ee

Comment by Githook User [ 18/Jan/18 ]

Author:

{'name': 'Kevin Albertson', 'email': 'kevin.albertson@10gen.com', 'username': 'kevinAlbs'}

Message: SERVER-31452 run fuzzer with shard stepdowns
Branch: master
https://github.com/mongodb/mongo/commit/e0febf2c258d77a179bdcf12ef8318ea92d12ee0

Comment by Kevin Duong [ 13/Nov/17 ]

Yeah, if it's not blocking the release, let's bump it to 3.7 Desired so the burndown chart is accurate.

Comment by Max Hirschhorn [ 13/Nov/17 ]

kevin.duong, this ticket captures extending the work to run the fuzzer with CSRS primary stepdowns from SERVER-30979 to run the fuzzer with shard stepdowns. It isn't possible to schedule it until SERVER-30979 is completed. I don't think we'll realistically block the MongoDB 3.6 release on whether this test happens or not that we may just want to change the fixVersion to "3.7 Desired".

Comment by Kevin Duong [ 13/Nov/17 ]

max.hirschhorn Should we have someone on the team look at this prior to 3.6?

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