[
https://issues.apache.org/jira/browse/CASSANDRA-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3673:
--------------------------------------
Component/s: (was: Core)
Tools
Priority: Minor (was: Major)
Affects Version/s: (was: 1.0.6)
(was: 0.8.0)
Fix Version/s: (was: 1.0.7)
Issue Type: New Feature (was: Bug)
Summary: Allow reduced consistency in sstableloader utility
(was: Issues in sstableloader utility)
1) For 1.1 we've updated the loader to not become a gossip peer
(CASSANDRA-3045), but for 1.0.x that's part of how it works. In the meantime,
do not use nodetool removetoken; just let it expire normally when it's done.
2) The loader is doing you a favor here; it's a lot cheaper to get the data on
all the machines in the first place, than to put it only some and repair later.
But, I suppose it's reasonable to have an option to reduce the effective
ConsistencyLevel here.
> Allow reduced consistency in sstableloader utility
> --------------------------------------------------
>
> Key: CASSANDRA-3673
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3673
> 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/(10.10.01.10)(This 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
