cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3673) Allow reduced consistency in sstableloader utility
Date Mon, 02 Jan 2012 14:48:30 GMT


Jonathan Ellis commented on CASSANDRA-3673:

I think I'd rather have a CL option so it can still raise an error if you think (say) just
one node is down but a second goes offline briefly as you run the loader.  But --skip-dead-nodes
would also be reasonable.
> Allow reduced consistency in sstableloader utility
> --------------------------------------------------
>                 Key: CASSANDRA-3673
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Samarth Gahire
>            Priority: Minor
>              Labels: cassandra, clustering, performance, sstableloader
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> Below are some of the issues I have been facing since I am using sstable-loader cassandra
utility in cassandra-0.8.2
> 1) We have configured the sstableloader on a different machine.Since we have loaded sstables
from this machine it has become a part of the cluster and except loading time it is always
unreachable in describe cluster.
>     a)As it is unreachable whenever I changes the schema it says this node is unreachable(but
its ok as schema change reflect over the other nodes)
>     b) The main problem is when I tried to remove the node out of the cluster using nodetool
removetoken ,the process stucks saying "RemovalStatus: Removing token (62676456546693435176060154681903071729).
Waiting for replication confirmation from [cassandra-1/( is the ip of loader
machine)]".As loader is part of the cluster and cassandra tries to stream the data from loader
machine and could not stream.
> So instead of making loader machine permanent part of the cluster can we make it temporarily
part of the cluster?
> 2)When any of the node is down or unreachable with thrift based client like pelop we
can insert the data into the cassandra cluster.But this is not the case with the sstable-loader.It
do not work(do not stream) when any of the nodes in the cluster is down or unreachable.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message