Split ConfigIncrement workload

Adds a new ConfigIncrement workload that tests the ability of the
configuration database to remain correct under minority node data loss
situations.
This commit is contained in:
Lukas Joswiak 2022-02-09 11:58:36 -08:00
parent e8354d82bd
commit 85da80a9ce
3 changed files with 22 additions and 2 deletions

View File

@ -184,6 +184,7 @@ if(WITH_PYTHON)
add_fdb_test(TEST_FILES rare/ClogUnclog.toml)
add_fdb_test(TEST_FILES rare/CloggedCycleWithKills.toml)
add_fdb_test(TEST_FILES rare/ConfigIncrement.toml)
add_fdb_test(TEST_FILES rare/ConfigIncrementWithKills.toml)
add_fdb_test(TEST_FILES rare/ConflictRangeCheck.toml)
add_fdb_test(TEST_FILES rare/ConflictRangeRYOWCheck.toml)
add_fdb_test(TEST_FILES rare/CycleRollbackClogged.toml)

View File

@ -1,6 +1,5 @@
[configuration]
configDB = 'paxos'
coordinators = 3
configDB = 'random'
[[test]]
testTitle = 'ConfigIncrement'
@ -14,3 +13,7 @@ testTitle = 'ConfigIncrement'
[[test.workload]]
testName = 'Attrition'
machinesToKill = 10
machinesToLeave = 3
reboot = true
testDuration = 10.0

View File

@ -0,0 +1,16 @@
[configuration]
configDB = 'paxos'
[[test]]
testTitle = 'ConfigIncrement'
[[test.workload]]
testName = 'ConfigIncrement'
incrementActors = 2
incrementsPerActor = 10
meanSleepWithinTransactions = 0.01
meanSleepBetweenTransactions = 0.1
[[test.workload]]
testName = 'Attrition'
reboot = false