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
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
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
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
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
Edward,
I change my seed node to use its route-able IP address as its own seed
instead of 127.0.0.1. I still, however, still see the same results when
running nodetool.
On Fri, Jun 3, 2011 at 11:37 AM, Edward Capriolo wrote:
>
>
> On Fri, Jun 3, 2011 at 12:21 PM, David McNelis > wrote:
>
>> I
On Fri, Jun 3, 2011 at 12:21 PM, 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 enable
