Dne 25.9.2011 9:29, Philippe napsal(a):
I have this happening on 0.8.x It looks to me as this happens when the node is under heavy load such as unthrottled compactions or a huge GC.
i have this problem too. Node down detection must be improved - increased timeouts a bit or make more tries before making decision. If node is under load (especially if there is swap activity), it is often marked unavailable.

Reply via email to