I suspect you ran into
https://issues.apache.org/jira/browse/CASSANDRA-1676. This is fixed in
soon-to-be-released 0.6.7.
I had also multiple keyspaces defined (> 20). All nodes were 64 bit, no
mixtures.
On Mon, Nov 8, 2010 at 8:23 PM, Dimitry Lvovsky wrote:
> We didn't solve it unfortunately and and ended up regenerating the entire
> cluster. But, if it helps anyone in the future, we too had multiple
> keyspaces
We didn't solve it unfortunately and and ended up regenerating the entire
cluster. But, if it helps anyone in the future, we too had multiple
keyspaces when we encountered the problem.
On Mon, Nov 8, 2010 at 5:47 PM, Marc Canaleta wrote:
> I have just solved the problem removing the second ke
I have just solved the problem removing the second keyspace (manually moving
its column families to the first). So it seems the problem appears when
having multiple keyspaces.
2010/11/8 Thibaut Britz
> Hi,
>
> No I didn't solve the problem. I reinitialized the cluster and gave each
> node manual
Hi,
No I didn't solve the problem. I reinitialized the cluster and gave each
node manually a token before adding data. There are a few messages in
multiple threads related to this, so I suspect it's very common and I hope
it's gone with 0.7.
Thibaut
On Sun, Nov 7, 2010 at 6:57 PM, Marc Canale
Hi,
Did you solve this problem? I'm having the same poblem. I'm trying to
bootstrap a third node in a 0.66 cluster. It has two keyspaces: Keyspace1
and KeyspaceLogs, both with replication factor 2.
It starts bootstrapping, receives some streams but it keeps waiting for
streams. I enabled the debu
Maybe your7000 is being blocked by iptables
or some firewall or maybe you have it bound ( tag ) to
localhost instead an ip address.
Hope this helps,
Dimitry.
On Thu, Oct 28, 2010 at 5:35 PM, Thibaut Britz <
thibaut.br...@trendiction.com> wrote:
> Hi,
>
> I have the same problem with 0.6.5
Hey Aaron,
> Are there any log messages in the existing nodes or the new one which
> mention each other?
>From the currently running nodes we get the message that the new is up:
INFO [GMFD:1] 2010-10-22 10:22:49,232 Gossiper.java (line 591) Node /
192.168.2.18 is now part of the cluster
INFO [GM
Hi,
I have the same problem with 0.6.5
New nodes will hang forever in bootstrap mode (no streams are being opened)
and the receiver thread just waits for data forever:
INFO [Thread-53] 2010-10-27 20:33:37,399 SSTableReader.java (line 120)
Sampling index for /hd2/cassandra/data/table_xyz/
table
The best approach is to manually select the tokens, see the Load Balancing
section http://wiki.apache.org/cassandra/Operations Also
Are there any log messages in the existing nodes or the new one which mention
each other?
Is this a production system? Is it still running ?
Sorry there is not
Hi Aaron,
Thanks for your reply.
We still haven't solved this unfortunately.
How did you start the bootstrap for the .18 node ?
Standard way: we set "AutoBootstrap" to true and added all the servers from
the working ring as seeds.
> Was it the .18 or the .17 node you tried to add
We first t
Dimitry, Did you get anywhere with this ? Was it the .18 or the .17 node you tried to add ? How did you start the bootstrap for the .18 node ? Does it have a token in the config or did you use nodetool move to set it? I had a quick look at the code AKAIK the message about removing the fat client i
Hi All,
We recently upgraded from .65 to .66 after which we tried adding a new node to
our cluster. We left it bootstrapping and after 3 days, it still refused to
join the ring. The strange thing is that nodetool info shows 50GB of load
and nodetool ring shows that it sees the rest of ring,
13 matches
Mail list logo
