Hi Andrew,
We were having problems with gossip TCP connections being held open and
changed our SOP for stopping cassandra to being:
nodetool disablegossip
nodetool drain
service cassandra stop
This seemed to close down the gossip cleanly (the nodetool drain is advised
as well) and meant that
tion based on this
> message or any information herein.
> If you have received this message in error, please advise the sender
> immediately by reply email and delete this message. Thank you.
>
--
*Ben Dalling** MSc, CEng, MBCS CITP*
League of Crafty Programmers Ltd
Mobile: +44 (0) 776 981-1900
email: b.dall...@locp.co.uk
www: http://www.locp.co.uk
http://www.linkedin.com/in/bendalling
Hi Simon,
See http://www.datastax.com/dev/blog/repair-in-cassandra for a good
explanation. Basically repair is not a good word because it suggests it is
fixing something that is broken. This is not the case. It ensures the
consistency across your cluster. Not running repairs is a VERY BAD