Something is not right if it thinks the rf is different. Do you have the
command you ran for repair and the error?
If you are willing to do the operation again I'd be interested to see if
nodetool cleanup causes any data to be removed (you should snapshot the
disks before running this as it will r
Hi all,
Sorry I couldn't update earlier as I got caught up in some other stuff.
Anyway, my previous 3 node cluster was on version 3.9. I created a new
cluster of cassandra 3.11.2 with same number of nodes on GCE VMs instead of
DC/OS. My existing cluster has cassandra data on persistent disks. I
Thanks for the response guys.
Let me try setting token ranges manually and move the data again to correct
nodes. Will update with the outcome soon.
On Tue, Apr 17, 2018 at 5:42 AM, kurt greaves wrote:
> Sorry for the delay.
>
>> Is the problem related to token ranges? How can I find out token
Sorry for the delay.
> Is the problem related to token ranges? How can I find out token range for
> each node?
> What can I do to further debug and root cause this?
Very likely. See below.
My previous cluster has 3 nodes but replication factor is 2. I am not
> exactly sure how I would handle the
*nodetool ring* will give you the tokens for each node on the ring. Each
node has the token range between the previous node's token and its token -
so the token range for each node is the interval (previous_token,
this_token]. The first node in the ring has the range between the last
node's token a
*UPDATE* - I created schema for all the tables in one of the keypsaces,
copied data to new directories and ran nodetool refresh. However, a lot of
data seems to be missing.
I ran nodetool repair on all three nodes one by one. First two nodes took
around 20 minutes (each) to complete. Third node to
Sorry for the late reply. I was trying to figure out some other approach to
it.
@Kurt - My previous cluster has 3 nodes but replication factor is 2. I am
not exactly sure how I would handle the tokens. Can you explain that a bit?
@Michael - Actually, my DC/OS cluster has an older version than my
Without looking at the code I'd say maybe the keyspaces are displayed
purely because the directories exist (but it seems unlikely). The process
you should follow instead is to exclude the system keyspaces for each node
and manually apply your schema, then upload your CFs into the correct
directory.
Michael,
both of the folders are with hash, so I dont think that would be an issue.
What is strange is why the tables dont show up if the keyspaces are
visible. Shouldnt that be a meta data that can be edited once and then be
visible?
Affan
- Affan
On Thu, Apr 5, 2018 at 7:55 PM, Michael Shule
On 04/05/2018 09:04 AM, Faraz Mateen wrote:
>
> For example, if the table is *data_main_bim_dn_10*, its data directory
> is named data_main_bim_dn_10-a73202c02bf311e8b5106b13f463f8b9. I created
> a new table with the same name through cqlsh. This resulted in creation
> of another directory with a
10 matches
Mail list logo
