There is a window after a node goes down that changes that node should have gotten will be kept. If the node is down LONGER than that, it will server stale data. If the consistency is greater than two, its data will be ignored (if consistency one, its data could be the first returned, if consistency two then the application needs to be able to handle such a situation. Nodetool repair needs to be run in this case to get data consistent. Cleanup does more than make things pretty, but it will do that.
The comment about disabling the thrift listener is related to preventing the node serving old data if the timeout I mention above has expired between the time the node comes on line and the time the repair is completed. One of the advantages of using e.g. Ansible is that it can be configured to whack an errant node's thrift listener BEFORE it starts the node's Cass instance. Agent based tools like Puppet and Chef can have this magic performed. This automatically start Cass vs. NOT automatically starting the service sometimes makes for interesting religious wars. And obviously if the node didn't stop but just lost network connections, there are advantages to agent based tools. *.......* *“Life should not be a journey to the grave with the intention of arriving safely in apretty and well preserved body, but rather to skid in broadside in a cloud of smoke,thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!” - Hunter ThompsonDaemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872* On Fri, Nov 27, 2015 at 3:51 AM, Hadmut Danisch <had...@danisch.de> wrote: > Thanks! > > Hadmut >
