On 3/15/12 9:16 AM, aaron morton wrote:
normally join-ring is only used when the node is having some sort of
problem.
The best approach to bringing up a new is to explicitly set the token
and start it with auto_bootstrap=true.
http://www.datastax.com/docs/1.0/operations/cluster_management#add
Ok I'll give it a try.
Thank you Aaron
On 3/15/12 9:16 AM, aaron morton wrote:
- use the join command
normally join-ring is only used when the node is having some sort of
problem.
The best approach to bringing up a new is to explicitly set the token
and start it with auto_bootstrap=true.
h
>> - use the join command
normally join-ring is only used when the node is having some sort of problem.
The best approach to bringing up a new is to explicitly set the token and start
it with auto_bootstrap=true.
http://www.datastax.com/docs/1.0/operations/cluster_management#adding-capacity-to-
I have to add that I didn't set the token too to let the cluster choose one
On 3/14/12 10:11 AM, Cyril Scetbon wrote:
To bootstap the node I :
- start a new node with auto_bootstrap=true and join-ring=false
- use the join command
and yes, when I use the join command the first time, it says it
To bootstap the node I :
- start a new node with auto_bootstrap=true and join-ring=false
- use the join command
and yes, when I use the join command the first time, it says it can't
find seed nodes, as I wrote in my first email
The logfiles I sent you have all this except that the join error
Can you provide some context for the log files please.
The original error had to do with bootstrapping a new node into a cluster. The
log looks like a node is starting with -Dcassadra.join-ring = false and then
nodetool join is run.
Is there an error when this runs ?
Cheers
---
Did you find something in the files I sent you ?
On 3/12/12 10:47 AM, aaron morton wrote:
Modify this line the log4j-server.properties. It will normally be
located in /etc/cassandra
https://github.com/apache/cassandra/blob/trunk/conf/log4j-server.properties#L21
Change INFO to DEBUG
Cheers
-
I don't know if it can helps, but the only thing I see on cluster's
nodes is :
==> /var/log/cassandra/output.log <==
INFO 10:57:28,530 InetAddress /10.0.1.70 is now dead.
when I try to join the node 10.0.1.70 to the cluster
On 3/12/12 11:27 AM, Cyril Scetbon wrote:
It's done.
Nothing new o
Modify this line the log4j-server.properties. It will normally be located in
/etc/cassandra
https://github.com/apache/cassandra/blob/trunk/conf/log4j-server.properties#L21
Change INFO to DEBUG
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/12/12 9:50 AM, aaron morton wrote:
It may be the case that the joining node does not have enough
information. But there is a default 30 second delay while the node
waits for the ring information to stabilise.
What version are you using ?
1.0.7
Next time you add a new node can you try i
It may be the case that the joining node does not have enough information. But
there is a default 30 second delay while the node waits for the ring
information to stabilise.
What version are you using ?
Next time you add a new node can you try it with logging set the DEBUG. If you
get the er
After more than 9 hours, I've restart the node and reused the join
command (data+cache+commitlog have not been erased) and now the node is
in normal state in less than a second :
nodetool -h localhost ring
Address DC RackStatus State Load
OwnsToken
Hi all,
When I try the join command I have the following error :
Exception in thread "main" java.lang.RuntimeException: No other nodes
seen! Unable to bootstrap.If you intended to start a single-node
cluster, you should make sure your broadcast_address (or listen_address)
is listed as a seed.
13 matches
Mail list logo
