On Thu, Aug 29, 2013 at 4:25 PM, Anthony Grasso wrote:
> Puppet was the first thing that came to mind for us as well. In addition,
> we had the same thought about auto-restarting nodes when the configuration
> is changed. If a configuration on all the nodes is changed, we would want
> to restart o
An alternative to cssh is fabric. It's very flexible in that you can
automate almost any repetitive task that you'd send to machines in a
cluster, and it's written in python, meaning if you're in AWS you can mix
it with boto to automate pretty much anything you want.
On Thu, Aug 29, 2013 at 4:25
Thanks Nate! We will look into this one to see if we can use it.
Regards,
Anthony
On Tue, Aug 27, 2013 at 12:22 AM, Nate McCall wrote:
>
>> For example, if I want to make some changes to the configuration file
>> that resides on each node, is there a tool that will propagate the change
>> to ea
Hi Particia,
Thank you for the feedback. It has been helpful.
On Tue, Aug 27, 2013 at 12:02 AM, Patricia Gorla
wrote:
> Anthony,
>
> We use a number of tools to manage our Cassandra cluster.
>
> * Datastax OpsCenter [0] for at a glance information, and trending
> statistics. You can also run op
>
>
> For example, if I want to make some changes to the configuration file that
> resides on each node, is there a tool that will propagate the change to
> each node?
>
> You may also want to take a look at Priam from the Netflix folks:
https://github.com/Netflix/Priam
Assumes AWS (though some of
Anthony,
We use a number of tools to manage our Cassandra cluster.
* Datastax OpsCenter [0] for at a glance information, and trending
statistics. You can also run operations through here, though I prefer
to use nodetool for any mutative operation.
* nodetool for ad hoc status checks, and day-to-d
