You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Dathan Pattishall <da...@gmail.com> on 2010/07/21 01:09:59 UTC
how come some nodes will drop nodes from the ring and not others?
dsh is a distributed shell that basically runs the same command on
multiple servers. Notice that cass03 sees all 4 servers, yet the other
3 only sees three servers? Storage-conf.xml is the same among all
nodes i.e.
<Seeds>
<Seed>10.129.28.14</Seed>
<Seed>10.129.28.20</Seed>
<Seed>10.129.28.22</Seed>
<Seed>10.129.28.23</Seed>
</Seeds>
cass01 == 10.129.28.14
cass02 == 10.129.28.20
cass03 == 10.129.28.22
cass04 == 10.129.28.23
dsh -eg cassandra "/opt/cassandra/bin/nodetool --host=localhost
--port=8181 ring"
cass01: Address Status Load Range
Ring
cass01:
149416040858059761249215819391553456957
cass01: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass01: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass01: 10.129.28.23 Up 2.03 GB
149416040858059761249215819391553456957 |-->|
cass02: Address Status Load Range
Ring
cass02:
149416040858059761249215819391553456957
cass02: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass02: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass02: 10.129.28.23 Up 2.03 GB
149416040858059761249215819391553456957 |-->|
cass03: Address Status Load Range
Ring
cass03:
149416040858059761249215819391553456957
cass03: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass03: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass03: 10.129.28.14 Up 5.83 GB
132300524084158455835439496737701548718 | |
cass03: 10.129.28.23 Up 1.86 GB
149416040858059761249215819391553456957 |-->|
cass04: Address Status Load Range
Ring
cass04:
149416040858059761249215819391553456957
cass04: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass04: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass04: 10.129.28.23 Up 2.03 GB
149416040858059761249215819391553456957 |-->|
Re: how come some nodes will drop nodes from the ring and not others?
Posted by Carlos Alvarez <cb...@gmail.com>.
On Tue, Jul 20, 2010 at 8:20 PM, Dathan Pattishall <da...@gmail.com> wrote:
> No did not copy the data directories from one node to another. This
> data is new data, newly created from scratch.
>
I ussualy see this behaviour after a node shutdown/startup but it
tends to disappear over time (sometimes over 24 hours).
Carlos.
Re: how come some nodes will drop nodes from the ring and not others?
Posted by Dathan Pattishall <da...@gmail.com>.
No did not copy the data directories from one node to another. This
data is new data, newly created from scratch.
On Tue, Jul 20, 2010 at 4:17 PM, Stu Hood <st...@rackspace.com> wrote:
> Did you copy the data directories from one node to the others? http://wiki.apache.org/cassandra/FAQ#cloned
>
> -----Original Message-----
> From: "Dathan Pattishall" <da...@gmail.com>
> Sent: Tuesday, July 20, 2010 6:09pm
> To: user@cassandra.apache.org
> Subject: how come some nodes will drop nodes from the ring and not others?
>
> dsh is a distributed shell that basically runs the same command on
> multiple servers. Notice that cass03 sees all 4 servers, yet the other
> 3 only sees three servers? Storage-conf.xml is the same among all
> nodes i.e.
>
> <Seeds>
> <Seed>10.129.28.14</Seed>
> <Seed>10.129.28.20</Seed>
> <Seed>10.129.28.22</Seed>
> <Seed>10.129.28.23</Seed>
> </Seeds>
>
>
> cass01 == 10.129.28.14
> cass02 == 10.129.28.20
> cass03 == 10.129.28.22
> cass04 == 10.129.28.23
>
>
> dsh -eg cassandra "/opt/cassandra/bin/nodetool --host=localhost
> --port=8181 ring"
> cass01: Address Status Load Range
> Ring
> cass01:
> 149416040858059761249215819391553456957
> cass01: 10.129.28.22 Up 11.91 GB
> 81142293380414172666166867532143840182 |<--|
> cass01: 10.129.28.20 Up 5.91 GB
> 115317719798097018520189339526900770000 | |
> cass01: 10.129.28.23 Up 2.03 GB
> 149416040858059761249215819391553456957 |-->|
> cass02: Address Status Load Range
> Ring
> cass02:
> 149416040858059761249215819391553456957
> cass02: 10.129.28.22 Up 11.91 GB
> 81142293380414172666166867532143840182 |<--|
> cass02: 10.129.28.20 Up 5.91 GB
> 115317719798097018520189339526900770000 | |
> cass02: 10.129.28.23 Up 2.03 GB
> 149416040858059761249215819391553456957 |-->|
> cass03: Address Status Load Range
> Ring
> cass03:
> 149416040858059761249215819391553456957
> cass03: 10.129.28.22 Up 11.91 GB
> 81142293380414172666166867532143840182 |<--|
> cass03: 10.129.28.20 Up 5.91 GB
> 115317719798097018520189339526900770000 | |
> cass03: 10.129.28.14 Up 5.83 GB
> 132300524084158455835439496737701548718 | |
> cass03: 10.129.28.23 Up 1.86 GB
> 149416040858059761249215819391553456957 |-->|
> cass04: Address Status Load Range
> Ring
> cass04:
> 149416040858059761249215819391553456957
> cass04: 10.129.28.22 Up 11.91 GB
> 81142293380414172666166867532143840182 |<--|
> cass04: 10.129.28.20 Up 5.91 GB
> 115317719798097018520189339526900770000 | |
> cass04: 10.129.28.23 Up 2.03 GB
> 149416040858059761249215819391553456957 |-->|
>
>
>
RE: how come some nodes will drop nodes from the ring and not others?
Posted by Stu Hood <st...@rackspace.com>.
Did you copy the data directories from one node to the others? http://wiki.apache.org/cassandra/FAQ#cloned
-----Original Message-----
From: "Dathan Pattishall" <da...@gmail.com>
Sent: Tuesday, July 20, 2010 6:09pm
To: user@cassandra.apache.org
Subject: how come some nodes will drop nodes from the ring and not others?
dsh is a distributed shell that basically runs the same command on
multiple servers. Notice that cass03 sees all 4 servers, yet the other
3 only sees three servers? Storage-conf.xml is the same among all
nodes i.e.
<Seeds>
<Seed>10.129.28.14</Seed>
<Seed>10.129.28.20</Seed>
<Seed>10.129.28.22</Seed>
<Seed>10.129.28.23</Seed>
</Seeds>
cass01 == 10.129.28.14
cass02 == 10.129.28.20
cass03 == 10.129.28.22
cass04 == 10.129.28.23
dsh -eg cassandra "/opt/cassandra/bin/nodetool --host=localhost
--port=8181 ring"
cass01: Address Status Load Range
Ring
cass01:
149416040858059761249215819391553456957
cass01: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass01: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass01: 10.129.28.23 Up 2.03 GB
149416040858059761249215819391553456957 |-->|
cass02: Address Status Load Range
Ring
cass02:
149416040858059761249215819391553456957
cass02: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass02: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass02: 10.129.28.23 Up 2.03 GB
149416040858059761249215819391553456957 |-->|
cass03: Address Status Load Range
Ring
cass03:
149416040858059761249215819391553456957
cass03: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass03: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass03: 10.129.28.14 Up 5.83 GB
132300524084158455835439496737701548718 | |
cass03: 10.129.28.23 Up 1.86 GB
149416040858059761249215819391553456957 |-->|
cass04: Address Status Load Range
Ring
cass04:
149416040858059761249215819391553456957
cass04: 10.129.28.22 Up 11.91 GB
81142293380414172666166867532143840182 |<--|
cass04: 10.129.28.20 Up 5.91 GB
115317719798097018520189339526900770000 | |
cass04: 10.129.28.23 Up 2.03 GB
149416040858059761249215819391553456957 |-->|