search

thelastpickle / cassandra-medusa

Apache Cassandra Backup and Restore Tool
Apache License 2.0
265 stars 143 forks source link

Configuring for a dynamic data directory #61

Open parham-pythian opened 4 years ago

parham-pythian commented 4 years ago

Project board link

We need to pass in a dynamic data directory different than configured in the yaml file. Is there a way to pass the data directory in any flag or the .ini? Alternatively, what is Medusa using the cassandra.yaml file for? (Could we feed it a different yaml than what Cassandra is using for startup?)

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: MED-91

arodrime commented 4 years ago

(Could we feed it a different yaml than what Cassandra is using for startup?)

Hello, the information for the data directory is indeed taken from Cassandra config file. You can indeed use a custom file, different from the one you started Cassandra with. Just use the path you want here: https://github.com/thelastpickle/cassandra-medusa/blob/master/medusa-example.ini#L18. The limitation I know about is that Medusa does not (yet) work with multiple data directories (ie. JBOD). If you want to use Medusa (and for a bunch of other reasons related to Cassandra), prefer a Raid0 usage of disks.

Yet I'm not sure to understand how having a new data path set (dynamically) would be useful. Would you let us know if this setting pointed above is good enough for you or if you need something else?

Also, this should be quite straightforward in any case, we have a lot of issues to handle, and this is far from being our top priority (maybe with more context we will reevaluate this position). If you want to go ahead and suggest a PR or at least an explanation of how you think it should be working and why, this would be appreciated @parham-pythian.

Thanks for the feedback!