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
On Tue, Feb 7, 2012 at 18:35, Brandon Williams wrote:
> Make sure you have JNA, without it the cost of forking ln to snapshot
> is expensive.
I assume JNA is enabled.
>From the output.log:
INFO 10:16:20,725 JNA mlockall successful
Regards,
P.
On Tue, Feb 7, 2012 at 2:17 AM, Patrik Modesto wrote:
> Hi,
>
> I've a strange problem with my test cluster. Calling truncate on a
> small ColumnFamily on idle cluster of 4 nodes returns
> UnavailableException after 10s. That 10s is set in rpc_timeout_in_ms.
Make sure you have JNA, without it the
Hi,
I've a strange problem with my test cluster. Calling truncate on a
small ColumnFamily on idle cluster of 4 nodes returns
UnavailableException after 10s. That 10s is set in rpc_timeout_in_ms.
All nodes are up and running, here is nodetool ring:
Address DC RackStatus S
