truncate will throw Unavailable when it times out waiting for one of the nodes to return.
The full error for the UnavailableException should include some text saying how many messages it received.
You can also check the logs on the other machines to see if they are erroring.
Finally turn up the log to DEBUG on the node you are running the truncate on and watch for log lines from the MessagingService .
On 8/02/2012, at 8:10 PM, Patrik Modesto wrote:
On Tue, Feb 7, 2012 at 18:35, Brandon Williams <firstname.lastname@example.org
Make sure you have JNA, without it the cost of forking ln to snapshot
I assume JNA is enabled.
From the output.log:
INFO 10:16:20,725 JNA mlockall successful