Thanks, will try to look into it.
Aaron
On 14 Mar 2011, at 20:43, Patrik Modesto wrote:
> On Fri, Mar 11, 2011 at 22:31, Aaron Morton wrote:
>> The assertion is interesting. Can you reproduce it with logging at debug and
>> post the results? Could you try to reproduce it with a clean cluster?
On Fri, Mar 11, 2011 at 22:31, Aaron Morton wrote:
> The assertion is interesting. Can you reproduce it with logging at debug and
> post the results? Could you try to reproduce it with a clean cluster?
It was on a clean cluster last time. Anyway I started clean cluster
again, repeated the same s
IMHO creating a keyspace with RF higher than the number of nodes sounds like a
bug. It puts the cluster into a bad place. It may even be a regression, will
take a look at the code.
The assertion is interesting. Can you reproduce it with logging at debug and
post the results? Could you try to re
Unfortunately I can't provide the info, I deleted it. It was in wery
strange state.
I started with new cluster today, 2 nodes, each with
auto_bootstrap:true. I can create a keyspace with RF=3, but I can't
insert any data in it. It didn't happen with the old cluster which
made me think. How could I
> Bootstrapping uses the same mechanisms as a repair to streams data from other
> nodes. This can be a heavy weight process and you may want to control when it
> starts.
>
> Joining the ring just tells the other nodes you exists and this is your token.
And in general, except when initially setti
> Could it be because once auto_bootstrap is off it's off forever?
I am not entirely sure if this answers your question (I revisisted the
thread history but I'm a bit confused myself):
If by that you mean that given a node which was started with
auto_bootstrap=false, and it successfully joined the
r and upgraded hector this morning.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/problem-with-bootstrap-tp6127315p6159679.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Can you include this info...
- output from nodetool ring for all nodes so we can see whats in the ring
- what you've run on the node you are trying to bring in
- the nodetool command you are trying to run
- error logs
In general asking the cluster to replicate data more times than the number of
d was kill -9 and then sudo cassandra to start the node.
>
I am still trying to see how to find the root cause of this behaviour. I
wonder if this were to happen in production how will we debug or what will
we do :(
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065
Hi,
I'm stil fighting the
Exception in thread "main" java.lang.IllegalStateException:
replication factor (3) exceeds number of endpoints (2).
When I have a 2-server cluster, create Keyspace with RF 3, I'm able to
add (without auto_bootstrap) another node but cluster nodetool
commands don't work a
hat that really means and what causes a node to remove? All I
did was kill -9 and then sudo cassandra to start the node.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/problem-with-bootstrap-tp6127315p6156250.html
Sent from the cassandra-u...@inc
his different than joining the ring? It will be good to see some
> example and the difference.
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/problem-with-bootstrap-tp6127315p6155334.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/problem-with-bootstrap-tp6127315p6155334.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
--
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/problem-with-bootstrap-tp6127315p6145100.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
ext:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/problem-with-bootstrap-tp6127315p6145100.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
I've seen this around a couple of times now.
On reason to fail if there is not enough nodes to meet the replication factor
is that CL.ALL requests cannot be processed. You could make the argument that
we can get into that state at any time is a node is down. But this error is
their never been
Hi,
I've small test cluster, 2 servers, both running successfully
cassandra 0.7.3. I've three keyspaces, two with RF1, one with RF3. Now
when I try to bootstrap 3rd server (empty initial_token,
auto_bootstrap: true), I get this exception on the new server.
INFO 23:13:43,229 Joining: getting boot
17 matches
Mail list logo