Introduce multi cycle tests for fast restore

This commit is contained in:
Meng Xu 2020-03-23 12:59:43 -07:00
parent 980037f3a8
commit ace19eefe4
1 changed files with 75 additions and 0 deletions

View File

@ -0,0 +1,75 @@
testTitle=BackupAndRestore
testName=Cycle
; nodeCount=30000
nodeCount=1000
transactionsPerSecond=2500.0
testDuration=30.0
expectedRate=0
clearAfterTest=false
keyPrefix=!
testName=Cycle
nodeCount=1000
transactionsPerSecond=2500.0
testDuration=30.0
expectedRate=0
clearAfterTest=false
keyPrefix=z
testName=Cycle
nodeCount=1000
transactionsPerSecond=2500.0
testDuration=30.0
expectedRate=0
clearAfterTest=false
keyPrefix=A
testName=Cycle
nodeCount=1000
transactionsPerSecond=2500.0
testDuration=30.0
expectedRate=0
clearAfterTest=false
keyPrefix=Z
; Each testName=RunRestoreWorkerWorkload creates a restore worker
; We need at least 3 restore workers: master, loader, and applier
testName=RunRestoreWorkerWorkload
; Test case for parallel restore
testName=BackupAndParallelRestoreCorrectness
backupAfter=10.0
restoreAfter=60.0
clearAfterTest=false
simBackupAgents=BackupToFile
; backupRangesCount<0 means backup the entire normal keyspace
backupRangesCount=-1
; TODO: Support abortAndRestartAfter test by commenting it out
abortAndRestartAfter=0
testName=RandomClogging
testDuration=90.0
; testName=Rollback
; meanDelay=90.0
; testDuration=90.0
; Do NOT consider machine crash yet
; testName=Attrition
; machinesToKill=10
; machinesToLeave=3
; reboot=true
; testDuration=90.0
; testName=Attrition
; machinesToKill=10
; machinesToLeave=3
; reboot=true
; testDuration=90.0
; Disable buggify for parallel restore
;buggify=off
;testDuration=360000 ;not work
;timeout is in seconds
timeout=360000