Hi Samuel,
thanks a lot for the jira link. Another reason to upgrade to 2.1 :-)
regards,
Christian
On Thu, Sep 10, 2015 at 1:28 PM, Samuel CARRIERE
wrote:
> Hi Christian,
> The problem you mention (violation of constency) is a true one. If I have
> understood
Hi Christian,
The problem you mention (violation of constency) is a true one. If I have
understood correctly, it is resolved in cassandra 2.1 (see
CASSANDRA-2434).
Regards,
Samuel
horschi a écrit sur 10/09/2015 12:41:41 :
> De : horschi
> A :
Hi Rob,
regarding 1-3:
Thank you for the step-by-step explanation :-) My mistake was to use
join_ring=false during the inital start already. It now works for me as its
supposed to. Nevertheless it does not what I want, as it does not take
writes during the time of repair/rebuild: Running an 8
>
>
> I've learned from experience that the node immediately joins the cluster,
>> and starts accepting reads (from other DCs) for the range it owns.
>
>
> This seems to be the incorrect assumption at the heart of the confusion.
> You "should" be able to prevent this behavior entirely via correct
On Wed, Sep 9, 2015 at 1:05 AM, Tom van den Berge wrote:
>
>> I've learned from experience that the node immediately joins the cluster,
>>> and starts accepting reads (from other DCs) for the range it owns.
>>
>>
>> This seems to be the incorrect assumption at the
Hi Tom,
"The idea of join_ring=false is that other nodes are not aware of the new
node, and therefore never send requests to it. The new node can then be
repaired"
Nicely explained, but I still see the issue that this node would not
receive writes during that time. So after the repair the node
>
> "one drawback: the node joins the cluster as soon as the bootstrapping
> begins."
> I am not sure I understand this correctly. It will get tokens, but not
> load data if you combine it with autobootstrap=false.
>
Joining the cluster means that all other nodes become aware of the new
node, and
> Running nodetool rebuild on a node that was started with join_ring=false
>> does not work, unfortunately. The nodetool command returns immediately,
>> after a message appears in the log that the streaming of data has started.
>> After that, nothing happens.
>
>
> Per driftx, the author of
On Tue, Sep 8, 2015 at 1:39 AM, horschi wrote:
> "The idea of join_ring=false is that other nodes are not aware of the new
> node, and therefore never send requests to it. The new node can then be
> repaired"
> Nicely explained, but I still see the issue that this node would
Hi Robert,
I tried to set up a new node with join_ring=false once. In my test that
node did not pick a token in the ring. I assume running repair or rebuild
would not do anything in that case: No tokens = no data. But I must admit:
I have not tried running rebuild.
Is a new node with
On Tue, Sep 8, 2015 at 2:39 PM, horschi wrote:
> I tried to set up a new node with join_ring=false once. In my test that
> node did not pick a token in the ring. I assume running repair or rebuild
> would not do anything in that case: No tokens = no data. But I must admit:
> I
Hi Christian,
No, I never tried survey mode. I didn't know it until now, but form the
info I was able to find it looks like it is meant for a different purpose.
Maybe it can be used to bootstrap a new DC, though.
On the other hand, the auto_bootstrap=false + rebuild scenario seems to be
designed
Hi Tom,
"one drawback: the node joins the cluster as soon as the bootstrapping
begins."
I am not sure I understand this correctly. It will get tokens, but not load
data if you combine it with autobootstrap=false.
How I see it: You should be able to start all the new nodes in the new DC
with
Running nodetool rebuild on a node that was started with join_ring=false
does not work, unfortunately. The nodetool command returns immediately,
after a message appears in the log that the streaming of data has started.
After that, nothing happens.
Tom
On Fri, Sep 12, 2014 at 5:47 PM, Robert
Hi Tom,
this sounds very much like my thread: "auto_bootstrap=false broken?"
Did you try booting the new node with survey-mode? I wanted to try this,
but I am waiting for 2.0.17 to come out (survey mode is broken in earlier
versions). Imho survey mode is what you (and me too) want: start a node,
Giving this some more thought, I think it's fair to say that using
LOCAL_ONE and LOCAL_QUORUM instead of ONE and QUORUM in this situation is a
actually workaround rather than a solution for this problem.
LOCAL_ONE and LOCAL_QUORUM are introduced to ensure that only the local DC
is used, which can
On Fri, Sep 12, 2014 at 6:57 AM, Tom van den Berge t...@drillster.com
wrote:
Wouldn't it be far more efficient if a node that is rebuilding itself is
responsible for not accepting reads until the rebuild is complete? E.g. by
marking it as Joining, similar to a node that is being bootstrapped?
When setting up a new (additional) data center, the documentation tells us
to use nodetool rebuild -- old dc to fill up the node(s) in the new dc,
and to disable auto_bootstrap.
I'm wondering if it is possible to fill the node with auto_bootstrap=true
instead of a nodetool rebuild command. If so,
Thanks, Rob.
I actually tried using LOCAL_ONE instead of ONE, but I still saw this
problem. Maybe I missed some queries when updating to LOCAL_ONE. Anyway,
it's good to know that this is supposed to work.
Tom
On Thu, Sep 11, 2014 at 10:28 PM, Robert Coli rc...@eventbrite.com wrote:
On Thu, Sep
19 matches
Mail list logo