Skip to main content

CassandraRestore Configuration

CassandraRestore Field Specification Reference

FieldDescriptionIs RequiredDefault
cassandraClusterThe CassandraCluster the restore is going to be used onY
cassandraBackupThe CassandraBackup the operator is going to restore to the cluster. If omitted the storageLocation, snapshotTag and secretName should be set.N
storageLocationLocation of SSTables. Example: protocol://myBucket. protocol can be gcp, s3, azure or oracleN
secretNameName of the secret where cloud storage credentials are locatedY
concurrentConnectionsnumber of threads used for upload, there might be at most so many uploading threads at any given timeN10
dcName of datacenter(s) against which restore will be done. It means that nodes in a different DC will not receive restore requests.N
entitiesdatabase entities to backup, it might be either only keyspaces or only tables (from different keyspaces if needed). E.g. 'k1,k2' if one wants to backup whole keyspaces and 'ks1.t1,ks2,t2' if one wants to backup tables.NAll keyspaces
timeoutnumber of hours to wait until backup is considered failed if not finished alreadyN5
noDeleteTruncatesflag saying if we should not delete truncated SSTables after they are imported, as part of CLEANUP phase, defaults to falseNfalse
noDeleteDownloadsflag saying if we should not delete downloaded SSTables from remote location, as part of CLEANUP phase, defaults to falseNfalse
noDownloadDataflag saying if we should not download data from remote location as we expect them to be there already, defaults to falseNfalse
importcontrols the SSTables import process. fields are taken from ColumnFamilyStoreMBean#importNewSSTablesNfalse
import.keepLevelNfalse
import.noVerifyNfalse
import.noVerifyTokensNfalse
import.noInvalidateCachesNfalse
import.quickif true, noVerifyTokens, noInvalidateCaches and noVerify will be set to true automaticallyNfalse
import.extendedVerifyNfalse
import.keepRepairedNfalse
resolveHostIdFromTopologyif set to true, host id of node to restore will be resolved from remote topology file located in a bucket by translating it from provided nodeId of storageLocation fieldNfalse
insecureRelevant during upload to S3-like bucket only. If true, communication is done via HTTP instead of HTTPS.Nfalse
skipBucketVerificationDo not check the existence of a bucket.Nfalse
retryRetry configuration for restore procedureN
retry.enabledEnable or disable retry mechanism on failureNfalse
retry.intervalTime gap between retries, linear strategy will have always this gap constant, exponential strategy will make the gap bigger exponentially (power of 2) on each attemptN
retry.strategyStrategy how retry should be driven, might be either 'LINEAR' or 'EXPONENTIAL'N
retry.maxAttemptsNumber of repetitions of an upload / download operation in case it fails before giving up completely.N
renameMap of key and values where keys and values are in format "keyspace.table", if key is "ks1.tb1" and value is "ks1.tb2", it means that upon restore, table ks1.tb1 will be restored into table ks1.tb2.N
schemaVersionversion of schema we want to restore fromN
exactSchemaVersionflag saying if we indeed want a schema version of a running node match with schema version a snapshot is taken onNfalse

See icarus/esop documentation for more information on the fields as most of them are passed directly to icarus.