Closed nbozic-zz closed 7 years ago
Here 4. is overkill since you need to supply cassandra-diagnostics.yaml configuration.
Deploying JARs as well as Cass restart depends on the actual Cass installation method (location of lib folders, the way Cass service is controlled, etc.). This info has to be provided to the installation script at the start.
@mgobec Cool way to do it, even though I think it will be hard for first iteration of installer, would be to ask Slow Query Module Y/N then when I hit Y to ask about threshold etc and generate yaml on the fly. If that is too much we should provide configuration yaml and ask about path or something.
Implemented in #222
People are having hard time to install and test our solution. We should create installer which will work easy and simple. Here are nice to haves and after some investigation we should have concrete idea what can and cannot be done. This should be wrapped in shell script.
cassandra-diagnostics.yaml
to place wherecassandra.yaml
iscassandra-env.sh
Do these steps for each node, so first step can be actually to provide somehow IPs of Cassandra nodes.