On 3/21/12 10:47 PM, Viktor Jevdokimov wrote:
This
is a known issue(s) to be fixed (can’t find exact tickets on
the tracker).
Controller,
that receives truncate command, checks all nodes up and
This is a known issue(s) to be fixed (can't find exact tickets on the tracker).
Controller, that receives truncate command, checks all nodes up and send
truncate message to all (including itself), waiting for an answer for
rpc_timeout_in_ms (will be fixed to separate timeout setting).
If any nod
I'd double-check the firewall on each node to make sure the storage and RPC
ports aren't being blocked.
We've found that "Up" in nodetool ring output reflects the gossip status, which
means only that one of the nodes can contact the node, not necessarily the
entire ring. It's possible for the e
run 'show keyspaces' in the cassandra-cli and paste the details for ks1
here.
On Wed, Mar 21, 2012 at 12:33 PM, Cyril Scetbon wrote:
> Hi,
>
> I'm using version 1.0.7 and when I try to truncate a CF in cqlsh it raises
> an error message, but it seems incorrect ...
>
> cqlsh:ks1> truncate core;
>
