Re: Nodetool ring and "Replicas" after 1.2 upgrade

To: user@cassandra.apache.org; Michael Theroux Sent: Tuesday, June 16, 2015 4:43 PM Subject: Re: Nodetool ring and "Replicas" after 1.2 upgrade Hi Michael, I barely can access internet right now and was not able to check outputs on my computer, yet first thing that come to my mind is t

Re: Nodetool ring and "Replicas" after 1.2 upgrade

i.apache.org/cassandra/FAQ#schema_disagreement). > > -Mike > > > -- > *From:* Jason Wee > *To:* user@cassandra.apache.org; Michael Theroux > *Sent:* Tuesday, June 16, 2015 12:07 AM > *Subject:* Re: Nodetool ring and "Replicas" after 1.2 u

Re: Nodetool ring and "Replicas" after 1.2 upgrade

: user@cassandra.apache.org; Michael Theroux Sent: Tuesday, June 16, 2015 12:07 AM Subject: Re: Nodetool ring and "Replicas" after 1.2 upgrade maybe check the system.log to see if there is any exception and/or error? check as well if they are having consistent schema for the key

Re: Nodetool ring and "Replicas" after 1.2 upgrade

ra 1.2.19. > Everything appears to be up and running normally, however, we have noticed > unusual output from nodetool ring. There is a new (to us) field "Replicas" > in the nodetool output, and this field, seemingly at random, is changing > from 2 to 3 and back to 2. &g

Nodetool ring and "Replicas" after 1.2 upgrade

Hello, We (finally) have just upgraded from Cassandra 1.1 to Cassandra 1.2.19.   Everything appears to be up and running normally, however, we have noticed unusual output from nodetool ring.  There is a new (to us) field "Replicas" in the nodetool output, and this field, seemingly at

Re: How to use nodetool ring only for one data center

When we have multi datacenter . In output datacenter like DC1 etc is not easy to associate with each node like we have RAC . On 28 April 2015 at 16:30, Rahul Neelakantan wrote: > Do you want this for some sort of reporting requirement? If so you may be > able to write a quick she'll script using

Re: How to use nodetool ring only for one data center

Do you want this for some sort of reporting requirement? If so you may be able to write a quick she'll script using grep to remove the unwanted data Rahul > On Apr 28, 2015, at 7:24 PM, Surbhi Gupta wrote: > > Hi, > > I wanted to know, how can we get the information of the token rings only fo

How to use nodetool ring only for one data center

Hi, I wanted to know, how can we get the information of the token rings only for one data centers when using vnodes and multiple data center. Thanks Surbhi

Re: Nodetool ring

Owns is how much of the entire, cluster wide, data set the node has. In both your examples every node has a full copy of the data. If you have 6 nodes and RF 3 they would have 50%. Cheers - Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassand

Re: Nodetool ring

Yes. On Fri, Jan 3, 2014 at 12:57 AM, Robert Coli wrote: > On Thu, Jan 2, 2014 at 10:48 AM, Vivek Mishra wrote: > >> Thanks for your quick reply. Even with 2 data center with 3 data nodes >> each i am seeing 100% on both data center nodes. >> > > Do you have RF=3 in both? > > =Rob > >

Re: Nodetool ring

On Thu, Jan 2, 2014 at 10:48 AM, Vivek Mishra wrote: > Thanks for your quick reply. Even with 2 data center with 3 data nodes > each i am seeing 100% on both data center nodes. > Do you have RF=3 in both? =Rob

Re: Nodetool ring

Thanks for your quick reply. Even with 2 data center with 3 data nodes each i am seeing 100% on both data center nodes. -Vivek On Fri, Jan 3, 2014 at 12:07 AM, Robert Coli wrote: > On Thu, Jan 2, 2014 at 10:20 AM, Vivek Mishra wrote: > >> I am trying to understand "Owns" here. AFAIK, it is

Re: Nodetool ring

On Thu, Jan 2, 2014 at 10:20 AM, Vivek Mishra wrote: > I am trying to understand "Owns" here. AFAIK, it is range(part of > keyspace). Not able to understand why is it shown as 100%? Is it because of > effective ownership? > When RF=N, effective ownership for each node is 100%. This is almost

Nodetool ring

Hi, I am trying to understand "Owns" here. AFAIK, it is range(part of keyspace). Not able to understand why is it shown as 100%? Is it because of effective ownership? Address RackStatus State LoadOwnsToken -3074457345618258503 x.x.x.x 3 Up Nor

Re: Output of "nodetool ring" with virtual nodes

That's cool! Many thanks! :-) 2013/10/15 Jon Haddad > It's expected. I think nodetool status is meant to replace nodetool ring. > > On Oct 15, 2013, at 11:45 AM, Paulo Motta > wrote: > > Hello, > > I recently did the "Enabling virtual nodes on an e

Re: Output of "nodetool ring" with virtual nodes

It's expected. I think nodetool status is meant to replace nodetool ring. On Oct 15, 2013, at 11:45 AM, Paulo Motta wrote: > Hello, > > I recently did the "Enabling virtual nodes on an existing production cluster" > procedure > (http://www.datastax.com/docum

Re: Output of "nodetool ring" with virtual nodes

Hi Paulo, Yes, that is expected. Now that you are using virtual nodes you should use "nodetool status" to see an output similar to what you saw with "nodetool ring" before you enabled virtual nodes. -Ike Walker On Oct 15, 2013, at 1

Output of "nodetool ring" with virtual nodes

Hello, I recently did the "Enabling virtual nodes on an existing production cluster" procedure ( http://www.datastax.com/documentation/cassandra/1.2/webhelp/cassandra/configuration/configVnodesProduction_t.html), and noticed that the output of the command "nodetool ring" c

Re: nodetool ring showing different 'Load' size

Ok. Thank you all you guys. Att. *Rodrigo Felix de Almeida* LSBD - Universidade Federal do Ceará Project Manager MBA, CSM, CSPO, SCJP On Wed, Jun 19, 2013 at 2:26 PM, Robert Coli wrote: > On Wed, Jun 19, 2013 at 5:47 AM, Michal Michalski > wrote: > > You can also perform a major compaction v

Re: nodetool ring showing different 'Load' size

On Wed, Jun 19, 2013 at 5:47 AM, Michal Michalski wrote: > You can also perform a major compaction via nodetool compact (for > SizeTieredCompaction), but - again - you really should not do it unless > you're really sure what you do, as it compacts all the SSTables together, > which is not somethin

Re: nodetool ring showing different 'Load' size

#x27;m facing a problem regarding to the size of the database. I performed a load phase and then, when running nodetool ring, I got the following output: *ubuntu@domU-12-31-39-0E-11-F1:~/cassandra$ bin/nodetool ring * *Address DC RackStatus Stat

Re: nodetool ring showing different 'Load' size

chmark on Cassandra and I'm facing a problem >> regarding to the size of the database. >>I performed a load phase and then, when running nodetool ring, I got >> the following output: >> >> *ubuntu@domU-12-31-39-0E-11-F1:~/cassandra$ bin/nodet

Re: nodetool ring showing different 'Load' size

>I performed a load phase and then, when running nodetool ring, I got > the following output: > > *ubuntu@domU-12-31-39-0E-11-F1:~/cassandra$ bin/nodetool ring * > *Address DC Rack

nodetool ring showing different 'Load' size

Hi, I've been running a benchmark on Cassandra and I'm facing a problem regarding to the size of the database. I performed a load phase and then, when running nodetool ring, I got the following output: *ubuntu@domU-12-31-39-0E-11-F1:~/cassandra$ bin/nodetool ring * *Address

Re: nodetool ring generate strange info

Looks like you are using vnodes, use nodetool status instead. Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 10/05/2013, at 11:58 PM, Nikolay Mihaylov wrote: > do you use vnodes ? > > > On Fri, May 10, 2013 at 1

Re: nodetool ring generate strange info

do you use vnodes ? On Fri, May 10, 2013 at 10:19 AM, 杨辉强 wrote: > Hi, all > I use ./bin/nodetool -h 10.21.229.32 ring > > It generates lots of info of same host like this: > > 10.21.229.32 rack1 Up Normal 928.3 MB24.80% >8875305964978355793 > 10.21.229.32 rack1

Re: nodetool ring generate strange info

same host, multiple cassandra instance? but looks wrong, what cassandra version? On Fri, May 10, 2013 at 3:19 PM, 杨辉强 wrote: > Hi, all > I use ./bin/nodetool -h 10.21.229.32 ring > > It generates lots of info of same host like this: > > 10.21.229.32 rack1 Up Normal 928.3 MB

Re: misreports on nodetool ring command on 1.1.4

@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Subject: Re: misreports on nodetool ring command on 1.1.4 What are the replication settings for the keyspace you created? Perhaps you used NTS with a bad DC name? On Wed, Feb 27, 2013 at 7:50 AM,

Re: misreports on nodetool ring command on 1.1.4

h node which makes > sense since RF=3 on everything I have. > > I brought up all 4 nodes in this cluster and ran nodetool ring and it > shows every node with 25%. > Then, I create a keyspace and run again and it shows every node at 0% > > Exact output was the following…..

misreports on nodetool ring command on 1.1.4

I just installed 1.1.4 as I need to test upgrade to 1.2.2. I have an existing 6 node cluster which shows 50% ownership on each node which makes sense since RF=3 on everything I have. I brought up all 4 nodes in this cluster and ran nodetool ring and it shows every node with 25%. Then, I

Re: new "nodetool ring" output and unbalanced ring?

en as a replica). >>> >>> To fix this, you'll either need to make the 1d node a 1c node, or make >>> 42535295865117307932921825928971026432 a 1d node so that you're alternating >>> racks within that DC. >>> >>> >>> On Thu, S

Re: new "nodetool ring" output and unbalanced ring?

to:ober...@civicscience.com>> wrote: Hi, I recently upgraded from 0.8.x to 1.1.x (through 1.0 briefly) and nodetool -ring seems to have changed from "owns" to "effectively owns". "Effectively owns" seems to

Re: new "nodetool ring" output and unbalanced ring?

o that you're alternating >> racks within that DC. >> >> >> On Thu, Sep 6, 2012 at 12:54 PM, William Oberman < >> ober...@civicscience.com> wrote: >> >>> Hi, >>> >>> I recently upgraded from 0.8.x to 1.1.x (through 1.0 briefly) a

Re: new "nodetool ring" output and unbalanced ring?

> On Thu, Sep 6, 2012 at 12:54 PM, William Oberman > wrote: > >> Hi, >> >> I recently upgraded from 0.8.x to 1.1.x (through 1.0 briefly) and >> nodetool -ring seems to have changed from "owns" to "effectively owns". >> "Effectively owns

Re: new "nodetool ring" output and unbalanced ring?

cks within that DC. On Thu, Sep 6, 2012 at 12:54 PM, William Oberman wrote: > Hi, > > I recently upgraded from 0.8.x to 1.1.x (through 1.0 briefly) and nodetool > -ring seems to have changed from "owns" to "effectively owns". > "Effectively owns" seems to

new "nodetool ring" output and unbalanced ring?

Hi, I recently upgraded from 0.8.x to 1.1.x (through 1.0 briefly) and nodetool -ring seems to have changed from "owns" to "effectively owns". "Effectively owns" seems to account for replication factor (RF). I'm ok with all of this, yet I still can't figur

Re: Unreachable node, not in nodetool ring

Hi, I finally successfully removed the "ghost" node using unsafeAssassinateEndpoint() as described there : http://tumblr.doki-pen.org/post/22654515359/assinating-cassandra-nodes, I hope this can help more people. Nodetool gossipinfo gives me now the following info for the ghost node : /10.56.62.

Re: Unreachable node, not in nodetool ring

t; > >>> ... > >>> > >>> > >>> I really thought this was going to work :-). > >>> > >>> > >>> Any other ideas ? > >>> > >>> > >>> Alain > >>> > >&g

Re: Unreachable node, not in nodetool ring

h you the best thanks for your >>> >>> help. >>> >>> >>> 2012/7/19 Olivier Mallassi : >>> >>> I got that a couple of time (due to DNS issues in our infra) >>> >>> >>> what you could try >>> >>&g

Re: Unreachable node, not in nodetool ring

.83.109 share the same token >> >> - if 10.56.62.211 is up, try decommission (via nodetool) >> >> - if not, move 10.59.21.241 or 10.58.83.109 to current token + 1 >> >> - use removetoken (via nodetool) to remove the token associated with >> >> 10.56.62.21

Re: Unreachable node, not in nodetool ring

en (via nodetool) to remove the token associated with > > 10.56.62.211. in case of failure, you can use removetoken -f instead. > > > then, the unreachable IP should have disappeared. > > > > HTH > > > On Thu, Jul 19, 2012 at 10:38 AM, Alain RODRIGUEZ > > wrote: > &

Re: Unreachable node, not in nodetool ring

ken associated with >>> 10.56.62.211. in case of failure, you can use removetoken -f instead. >>> >>> then, the unreachable IP should have disappeared. >>> >>> >>> HTH >>> >>> On Thu, Jul 19, 2012 at 10:38 AM, Alain RODRIGUEZ

Re: Unreachable node, not in nodetool ring

k with an other node but now when I describe cluster on cli I got >>> this : >>> >>> Cluster Information: >>>Snitch: org.apache.cassandra.locator.Ec2Snitch >>>Partitioner: org.apache.cassandra.dht.RandomPartitioner >>>Schema versions: >>

Re: Unreachable node, not in nodetool ring

tion: >>Snitch: org.apache.cassandra.locator.Ec2Snitch >>Partitioner: org.apache.cassandra.dht.RandomPartitioner >>Schema versions: >> UNREACHABLE: [10.56.62.211] >> e7e0ec6c-616e-32e7-ae29-40eae2b82ca8: [10.59.21.241, 10.58.83.109] >> >> And

Re: Unreachable node, not in nodetool ring

andra.dht.RandomPartitioner >Schema versions: > UNREACHABLE: [10.56.62.211] > e7e0ec6c-616e-32e7-ae29-40eae2b82ca8: [10.59.21.241, 10.58.83.109] > > And nodetool ring gives me : > > Address DC Rack

Unreachable node, not in nodetool ring

versions: UNREACHABLE: [10.56.62.211] e7e0ec6c-616e-32e7-ae29-40eae2b82ca8: [10.59.21.241, 10.58.83.109] And nodetool ring gives me : Address DC RackStatus State Load OwnsToken 85070591730234615865843651857942052864 10.59.21.241

Re: nodetool ring runs very slow

ssandra will now flush up to the two largest memtables to > free up memory. Adjust flush_largest_memtables_at threshold in > cassandra.yaml if you don't want Cassandra to do this automatically > > Feng Qu > From: Jonathan Ellis > To: user > Cc: Feng Qu > Sent: Frida

Re: nodetool ring runs very slow

gt;To: user >Cc: Feng Qu >Sent: Friday, February 24, 2012 2:29 PM >Subject: Re: nodetool ring runs very slow > >Read the server log and look for GCInspector output. > >On Fri, Feb 24, 2012 at 11:02 AM, Feng Qu wrote: >> Hi Jonathan, how to check out whether it'

Re: nodetool ring runs very slow

Haven't received any reply. Resend...   Feng Qu > > From: Feng Qu >To: Cassandra User Group >Sent: Wednesday, February 22, 2012 1:49 PM >Subject: nodetool ring runs very slow > > >We noticed that nodetool ring sometimes returns i

Re: nodetool ring runs very slow

st node in a 6-node ring and it has opscenter > community running on it. > > Feng Qu > > > From: Jonathan Ellis > To: user@cassandra.apache.org; Feng Qu > Sent: Thursday, February 23, 2012 1:19 PM > Subject: Re: nodetool ring runs very

Re: 1.0.2 - nodetool ring and info reports wrong load after compact

On Thu, Feb 23, 2012 at 7:29 AM, Bill Au wrote: > > Upgrade within the 1.0.x branch is simply a rolling restart, right? Generally, but you should always read NEWS.txt before upgrading. -- Tyler Hobbs DataStax

Re: nodetool ring runs very slow

The only time I've seen nodetool be that slow is when it was talking to a machine that was either swapping or deep into (JVM) GC storming. On Wed, Feb 22, 2012 at 3:49 PM, Feng Qu wrote: > We noticed that nodetool ring sometimes returns in 17-20 sec while it > normally runs in less

Re: 1.0.2 - nodetool ring and info reports wrong load after compact

ered compaction. After running a > > "nodetool compact", I noticed that on about half of the machines in my > > cluster, both "nodetool ring" and "nodetool info" report that the load is > > actually higher than before when I expect it to be lower. I

nodetool ring runs very slow

We noticed that nodetool ring sometimes returns in 17-20 sec while it normally runs in less than a sec. There were some compaction running when it happened. Did compaction cause nodetool slowness? Anything else I should check? >>> time nodetool -h hostname ring real 0m17.595s user

Re: 1.0.2 - nodetool ring and info reports wrong load after compact

CASSANDRA-3496, fixed in 1.0.4+ On Thu, Feb 16, 2012 at 8:27 AM, Bill Au wrote: > I am running 1.0.2 with the default tiered compaction.  After running a > "nodetool compact", I noticed that on about half of the machines in my > cluster, both "nodetool ring" and &q

Re: 1.0.2 - nodetool ring and info reports wrong load after compact

orton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 17/02/2012, at 3:27 AM, Bill Au wrote: > > I am running 1.0.2 with the default tiered compaction. After running a > "nodetool compact", I noticed that on about half of the machines in my > c

Re: 1.0.2 - nodetool ring and info reports wrong load after compact

the default tiered compaction. After running a > "nodetool compact", I noticed that on about half of the machines in my > cluster, both "nodetool ring" and "nodetool info" report that the load is > actually higher than before when I expect it to be lower. I

1.0.2 - nodetool ring and info reports wrong load after compact

I am running 1.0.2 with the default tiered compaction. After running a "nodetool compact", I noticed that on about half of the machines in my cluster, both "nodetool ring" and "nodetool info" report that the load is actually higher than before when I expect it to be

Re: Multiple data center nodetool ring output display 0% owns

> There was a thread on this a couple days ago -- short answer, the 'owns %' > column is effectively incorrect when you're using multiple DCs.  If you had > all 3 servers in 1 DC, since server YYY has token 1 and server XXX has token > 0, then server XXX would truly 'own' 0% (actually, 1/(2^128)

Re: Multiple data center nodetool ring output display 0% owns

so that would be even as well (assuming you replicate to both sites). --DRS On Feb 12, 2012, at 5:42 PM, Roshan wrote: > Hi > > I have deployed Cassandra 1.0.6 to a 2 data center and one data center (DC1) > having one node and the other data center (DC2) having two nodes. But when I >

Multiple data center nodetool ring output display 0% owns

Hi I have deployed Cassandra 1.0.6 to a 2 data center and one data center (DC1) having one node and the other data center (DC2) having two nodes. But when I do a nodetool ring using one IP, the output says 0% owns of DC1 node. Please see the output below. # sh nodetool -h 10.XXX.XXX.XX ring

Re: Nodetool ring and multiple dc

Thanks David, for the clarification. I feel it would be better if nodetool ring reports per-dc token space ownerships to correctly reflect what cassandra is internally doing, instead of global token space ownership. - Ravi On Fri, Feb 10, 2012 at 12:42 PM, David Schairer wrote: > nodetool r

Re: Nodetool ring and multiple dc

nodetool ring is, IMHO, quite confusing in the case of multiple datacenters. Might be easier to think of it as two rings: in your DC1 ring you have two nodes, and since the tokens are balanced, assuming your rows are randomly distributed you'll have half the data on each, since

Nodetool ring and multiple dc

Hi, I was trying to setup a backup DC from existing DC. State of existing DC with SimpleStrategy & rep_factor=1. ./nodetool -h localhost ring Address DC RackStatus State LoadOwns Token 85070591730234615865843651857942052864 XXX.YYYDC1

Re: nodetool ring question

p://www.thelastpickle.com > > On 18/01/2012, at 10:58 PM, Michael Vaknine wrote: > > I did restart the cluster and now it is normal 5GB. > ** ** > *From:* R. Verlangen [mailto:ro...@us2.nl] > *Sent:* Wednesday, January 18, 2012 11:32 AM > *To:* user@cassandra.apache.org

Re: nodetool ring question

..@us2.nl] > Sent: Wednesday, January 18, 2012 11:32 AM > To: user@cassandra.apache.org > Subject: Re: nodetool ring question > > I also have this problem. My data on nodes grows to roughly 30GB. After a > restart only 5GB remains. Is a factor 6 common for Cassandra? > > 20

RE: nodetool ring question

I did restart the cluster and now it is normal 5GB. From: R. Verlangen [mailto:ro...@us2.nl] Sent: Wednesday, January 18, 2012 11:32 AM To: user@cassandra.apache.org Subject: Re: nodetool ring question I also have this problem. My data on nodes grows to roughly 30GB. After a restart only

Re: nodetool ring question

Would be interesting to > know if it's wrong from the start or drifts during streaming or compaction. > > Cheers > > - > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 18/01/2012, at 12:04 PM, Jeremiah Jord

Re: nodetool ring question

12:04 PM, Jeremiah Jordan wrote: > There were some nodetool ring load reporting issues with early version of > 1.0.X don't remember when they were fixed, but that could be your issue. Are > you using compressed column families, a lot of the issues were with those. >

Re: nodetool ring question

There were some nodetool ring load reporting issues with early version of 1.0.X don't remember when they were fixed, but that could be your issue. Are you using compressed column families, a lot of the issues were with those. Might update to 1.0.7. -Jeremiah On 01/16/2012 04:04 AM, Mi

Re: nodetool ring question

). Cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 16/01/2012, at 11:04 PM, Michael Vaknine wrote: > Hi, > > I have a 4 nodes cluster 1.0.3 version > > This is what I get when I run nodetool ring > > Address

nodetool ring question

Hi, I have a 4 nodes cluster 1.0.3 version This is what I get when I run nodetool ring Address DC RackStatus State LoadOwns Token 127605887595351923798765477786913079296 10.8.193.87 datacenter1 rack1 Up Normal 46.47 GB 25.00% 0

Re: sstable count=0, why nodetool ring is not 0

I count the disk usage. I found that from nodetool information, space used (live) is about the nodetool ring info. space used(total) is about the disk usage. thx On Thu, Dec 8, 2011 at 9:53 AM, 祝海通 wrote: > > We are testing the the performance of Cassandra for Big Data. Now I also >

Re: sstable count=0, why nodetool ring is not 0

400GB of data? > > Thanks > -- > Dotan, @jondot <http://twitter.com/jondot> > > > > On Wed, Dec 7, 2011 at 5:57 AM, 祝海通 wrote: > >> hi,all >> >> We are using Cassandra 1.0.2. I am testing the TTL with loading 400G. >> When all the data are e

Re: sstable count=0, why nodetool ring is not 0

ired, I waited for some hours. > Later, the nodetool ring is still have 90GB. So I made a major compaction. > Then there are 30GB from the nodetool ring. After I saw the file system,I > found there are zero sstable. > I don't know where comes the 30GB? > > Best Regards >

Re: sstable count=0, why nodetool ring is not 0

hi,all > > We are using Cassandra 1.0.2. I am testing the TTL with loading 400G. > When all the data are expired, I waited for some hours. > Later, the nodetool ring is still have 90GB. So I made a major compaction. > Then there are 30GB from the nodetool ring. After I saw the file sys

sstable count=0, why nodetool ring is not 0

hi,all We are using Cassandra 1.0.2. I am testing the TTL with loading 400G. When all the data are expired, I waited for some hours. Later, the nodetool ring is still have 90GB. So I made a major compaction. Then there are 30GB from the nodetool ring. After I saw the file system,I found there are

Re: nodetool ring Load column

gt; include how you are configured in any JIRA you make, someone else was seeing > a similar issue with compression turned on. > > -Jeremiah > > On Oct 14, 2011, at 1:13 PM, Ramesh Natarajan wrote: > >> What does the Load column in nodetool ring mean?  From the output >&g

Re: nodetool ring Load column

in nodetool ring mean? From the output > below it shows 101.62 GB. However if I do a disk usage it is about 6 > GB. > > thanks > Ramesh > > > [root@CAP2-CNode1 cassandra]# > ~root/apache-cassandra-1.0.0-rc2/bin/nodetool -h localhost ring > Address DC

Re: nodetool ring Load column

some repo steps or some other data. Thanks - Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 15/10/2011, at 7:13 AM, Ramesh Natarajan wrote: > What does the Load column in nodetool ring mean? From the output > below it shows 101.62

nodetool ring Load column

What does the Load column in nodetool ring mean? From the output below it shows 101.62 GB. However if I do a disk usage it is about 6 GB. thanks Ramesh [root@CAP2-CNode1 cassandra]# ~root/apache-cassandra-1.0.0-rc2/bin/nodetool -h localhost ring Address DC RackStatus

Re: Nodetool ring not showing all nodes in cluster

LocationInfo CF > 3 - ensure the seed list for ALL nodes points to node A. > 4 - ensure the initial token is set correctly for B and C > 5 - start B and C one at a time and make sure nodetool ring and describe > cluster; in the CLI agree before starting the next > > *IF* node A ha

Re: Nodetool ring not showing all nodes in cluster

the first one (called A). 2 - Delete their LocationInfo CF 3 - ensure the seed list for ALL nodes points to node A. 4 - ensure the initial token is set correctly for B and C 5 - start B and C one at a time and make sure nodetool ring and describe cluster; in the CLI agree before starting the

Re: Nodetool ring not showing all nodes in cluster

I corrected the seed list and checked the cluster name. They are all good now. But still nodetool -ring shows only one node. INFO 21:36:59,735 Starting Messaging Service on port 7000 INFO 21:36:59,748 Using saved token 113427455640312814857969558651062452224 Nodes a_ipadrr and b_ipaddr have

Re: Nodetool ring not showing all nodes in cluster

or all 3 nodes since they all have >> the correct data and do not hav to migrate data from any particular >> node. >> >> My problem here is why does n't nodetool ring show me all nodes in the >> ring ? I agree that the cluster thinks that only one node is present. &g

Re: Nodetool ring not showing all nodes in cluster

ist of A is localhost. Seedlist of B is > localhost, A_ipaddr and seedlist of C is localhost,B_ipaddr,A_ipaddr. > I have autobootstrap set to false for all 3 nodes since they all have > the correct data and do not hav to migrate data from any particular > node. > > My problem here

Re: Nodetool ring not showing all nodes in cluster

; practice. > Try >> >>  The seedlist of A : A_ipaddr. >> >> Seedlist of B : A_ipaddr >> >> seedlist of C : A_ipaddr That does not work either. Once and do the above and invoke nodetool ring, it still shows only one node. Thanks, Aishwarya

Re: Nodetool ring not showing all nodes in cluster

> > The seedlist of A is localhost. Seedlist of B is localhost, A_ipaddr and seedlist of C is localhost,B_ipaddr,A_ipaddr. > Using localhost(or own IP address for non-seed nodes) is not a good practice. Try > The seedlist of A : A_ipaddr. Seedlist of B : A_ipaddr seedlist of C : A_ipaddr

Re: Nodetool ring not showing all nodes in cluster

hav to migrate data from any particular node. My problem here is why does n't nodetool ring show me all nodes in the ring ? I agree that the cluster thinks that only one node is present. How do I fix this ? Thanks, Aishwarya On Tue, Aug 2, 2011 at 9:56 AM, samal wrote: > > >&

Re: Nodetool ring not showing all nodes in cluster

; 100% of the load." > Cluster think only one node is present in ring, it doesn't agree RF=3 it is expecting RF=1. Original Q: I m not exactly sure what is the problem. But Does nodetool ring show all the host? What is your seed list? Is bootstrapped node has seed ip of its own?

Re: Nodetool ring not showing all nodes in cluster

system keyspace, bring the cluster up and bootstrap the nodes. > >> > >> > >> Kind regards, > >> Sorin > >> > >> > >> On Tue, Aug 2, 2011 at 2:53 PM, Aishwarya Venkataraman > >> wrote: > >>> > >>> Hello,

Re: Nodetool ring not showing all nodes in cluster

; Hello, >>> >>> I recently migrated 400 GB of data that was on a different cassandra >>> cluster (3 node with RF= 3) to a new cluster. I have a 3 node  cluster >>> with replication factor set to three. When I run nodetool ring, it >>> does not show me all the no

Re: Nodetool ring not showing all nodes in cluster

a >> cluster (3 node with RF= 3) to a new cluster. I have a 3 node  cluster >> with replication factor set to three. When I run nodetool ring, it >> does not show me all the nodes in the cluster. It always keeps showing >> only one node and mentions that it is handling 100% of t

Re: Nodetool ring not showing all nodes in cluster

ave a 3 node cluster > with replication factor set to three. When I run nodetool ring, it > does not show me all the nodes in the cluster. It always keeps showing > only one node and mentions that it is handling 100% of the load. But > when I look at the logs, the nodes are able to talk

Nodetool ring not showing all nodes in cluster

Hello, I recently migrated 400 GB of data that was on a different cassandra cluster (3 node with RF= 3) to a new cluster. I have a 3 node cluster with replication factor set to three. When I run nodetool ring, it does not show me all the nodes in the cluster. It always keeps showing only one

Re: Setting up cluster and nodetool ring in 0.8.0

Just to close this out, in case anyone was interested... my problem was firewall related, in that I didn't have my messaging/data port (7000) open on my seed node. Allowing traffic on this port resolved my issues. On Fri, Jun 3, 2011 at 1:43 PM, David McNelis wrote: > Thanks, Jonathan. Both

Re: Setting up cluster and nodetool ring in 0.8.0

Thanks, Jonathan. Both machines do have the exact same seed list. On Fri, Jun 3, 2011 at 1:39 PM, Jonathan Ellis wrote: > On Fri, Jun 3, 2011 at 11:21 AM, David McNelis > wrote: > > I want to make sure I'm not seeing things from a weird perspective. I > have > > two Cassandra instances where

Re: Setting up cluster and nodetool ring in 0.8.0

On Fri, Jun 3, 2011 at 11:21 AM, David McNelis wrote: > I want to make sure I'm not seeing things from a weird perspective.  I have > two Cassandra instances where one is set to be the seed, with autobootstap > disabled and its seed being 127.0.0.1. > The second instance has autobootstrap enabled

Re: Setting up cluster and nodetool ring in 0.8.0

set the token values for you nodes? I remember having similar > symptoms when I had a token conflict. > > -- > *From: *"David McNelis" > *To: *user@cassandra.apache.org > *Sent: *Friday, June 3, 2011 5:06:10 PM > *Subject: *Re: Setting up

Re: Setting up cluster and nodetool ring in 0.8.0

Did you set the token values for you nodes? I remember having similar symptoms when I had a token conflict. - Original Message - From: "David McNelis" To: user@cassandra.apache.org Sent: Friday, June 3, 2011 5:06:10 PM Subject: Re: Setting up cluster and nodetool rin

  1   2   >