wbtiger
/
foundationdb
mirror of https://github.com/apple/foundationdb.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
foundationdb/tests/ParallelRestoreApiCorrectne...

37 lines
846 B
Plaintext
Raw Normal View History

Add ParallelRestoreOldBackupApiCorrectnessAtomicRestore.txt Add tests/ParallelRestoreApiCorrectnessAtomicRestore.txt back which was mistakenly deleted in the previous commit.
2020-03-31 12:57:03 +08:00
testTitle=ApiCorrectnessTest
clearAfterTest=false
simBackupAgents=BackupToFile
Make the testspec more restrictive in terms of what can be set where. Testspec is currently very permissive in very misleading ways. In particular, the tester parser itself will swallow K=V settings and apply them at the test level, which breaks how a person would expect the scoping to work. Other settings apply to the entire simulation run globally, but appear to be workload specific. Even further, others affect simulation cluster creation or test harness behavior, but can again be set anywhere in a testspec. This changes testspec parsing to error if a setting that applies globally is anywhere but the top of the file, or if a setting that applies test-wide is applied to a workload instead of a test.
2020-07-06 17:03:30 +08:00
;timeout is in seconds
timeout=360000
runSetup=true
Add ParallelRestoreOldBackupApiCorrectnessAtomicRestore.txt Add tests/ParallelRestoreApiCorrectnessAtomicRestore.txt back which was mistakenly deleted in the previous commit.
2020-03-31 12:57:03 +08:00
Make the testspec more restrictive in terms of what can be set where. Testspec is currently very permissive in very misleading ways. In particular, the tester parser itself will swallow K=V settings and apply them at the test level, which breaks how a person would expect the scoping to work. Other settings apply to the entire simulation run globally, but appear to be workload specific. Even further, others affect simulation cluster creation or test harness behavior, but can again be set anywhere in a testspec. This changes testspec parsing to error if a setting that applies globally is anywhere but the top of the file, or if a setting that applies test-wide is applied to a workload instead of a test.
2020-07-06 17:03:30 +08:00
testName=ApiCorrectness
numKeys=5000
onlyLowerCase=true
shortKeysRatio=0.5
minShortKeyLength=1
maxShortKeyLength=3
minLongKeyLength=1
maxLongKeyLength=128
minValueLength=1
maxValueLength=1000
numGets=1000
numGetRanges=100
numGetRangeSelectors=100
numGetKeys=100
numClears=100
numClearRanges=10
maxTransactionBytes=500000
randomTestDuration=60
testName=AtomicRestore
startAfter=10.0
restoreAfter=50.0
fastRestore=true
usePartitionedLogs=true
; Each testName=RunRestoreWorkerWorkload creates a restore worker
; We need at least 3 restore workers: master, loader, and applier
testName=RunRestoreWorkerWorkload
Add ParallelRestoreOldBackupApiCorrectnessAtomicRestore.txt Add tests/ParallelRestoreApiCorrectnessAtomicRestore.txt back which was mistakenly deleted in the previous commit.
2020-03-31 12:57:03 +08:00