Skip to content
This repository has been archived by the owner on Oct 20, 2022. It is now read-only.

Enforce HARDLINKS restore strategy as it is faster #290

Merged
merged 3 commits into from
Jan 26, 2021

Conversation

cscetbon
Copy link
Contributor

IMPORT restore strategy implies reading sstables and rewriting them which is longer that using hardlinks. That PR enforces that choice.

Copy link
Contributor

@PERES-Richard PERES-Richard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be also removed :

"restorationStrategyType": restorationStrategyType,

And also the doc should be updated as well
https://github.com/Orange-OpenSource/casskop/blob/restore-strategy/website/docs/6_references/6_cassandra_restore.md

(in YAML example & table row)

@cscetbon
Copy link
Contributor Author

cscetbon commented Jan 18, 2021

@PERES-Richard I agree on the doc but not on the test. It's the response returned by the client and it always includes the restore strategy

@PERES-Richard
Copy link
Contributor

PERES-Richard commented Jan 19, 2021

@PERES-Richard I agree on the doc but not on the test. It's the response returned by the client and it always includes the restore strategy

Okey. I will test this new implem on our cluster to strongly make sure that this will not break backup & restore flows :)

@PERES-Richard PERES-Richard merged commit 8a12e02 into master Jan 26, 2021
@cscetbon cscetbon deleted the restore-strategy branch January 26, 2021 17:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants