cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Gahire (Created) (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-3673) Issues in sstableloader utility
Date Mon, 26 Dec 2011 10:27:31 GMT
Issues in sstableloader utility

                 Key: CASSANDRA-3673
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.0.6, 0.8.0
            Reporter: Samarth Gahire
             Fix For: 1.0.7

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