I think reading the relevant documentation might have helped.
http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html
On Fri, Aug 7, 2015 at 9:04 AM, horschi wrote:
> Hi Cyril,
>
> thanks for backing me up. I'm under siege from all sides here ;-)
>
>
> That
Hi Cyril,
thanks for backing me up. I'm under siege from all sides here ;-)
That something we're trying to do too. However disabling clients
> connections (closing thrift and native ports) does not prevent other nodes
> (acting as a coordinators) to request it ... Honestly we'd like to restart
>
Jeff,
That something we're trying to do too. However disabling clients connections
(closing thrift and native ports) does not prevent other nodes (acting as a
coordinators) to request it ... Honestly we'd like to restart a node that need
to deploy HH and to make it serve reads only when it's do
Hi Jeff,
You’re trying to force your view onto an established ecosystem.
>
It is not my intent to force anyone to do anything. I apologize if my title
was too provocative. I just wanted to clickbait ;-)
It’s not “wrong only because its currently bootstrapping”, it’s not
> bootstrapping at all,
To: "user@cassandra.apache.org"
Subject: Re: auto_bootstrap=false broken?
Hi Rob,
Your asking the wrong nodes for data in the rebuild-a-new-DC case does not
indicate a problem with the auto_bootstrap false + rebuild paradigm.
The node is "wrong" only because its currently bo
Hi Rob,
> Your asking the wrong nodes for data in the rebuild-a-new-DC case does not
> indicate a problem with the auto_bootstrap false + rebuild paradigm.
>
The node is "wrong" only because its currently bootstrapping. So imho
Cassandra should not serve any reads in such a case.
>
> What ma
On Wed, Aug 5, 2015 at 2:08 AM, horschi wrote:
> So what I am trying to say is: Everytime you use auto_bootstrap=false, you
> are entering a dangerous path. And I think this could be fixed, if
> auto_bootstrap=false would leave the node in a write-only state. Then the
> operator could still decid
Hi Rob,
let me try to give examples why auto_bootstrap=false is dangerous:
I just yesterday had the issue that we wanted to set up a new DC:
Unfortunetaly we had one application that used CL.ONE (because its only
querying static data and its read heavy). That application stopped working
after we
On Tue, Aug 4, 2015 at 11:40 AM, horschi wrote:
> unless you specify auto_bootstrap=false :)
>
... so why are you doing that?
Two experts are confused as to what you're trying to do; why do you think
you need to do it?
=Rob
Hi Jonathan,
unless you specify auto_bootstrap=false :)
kind regards,
Christian
On Tue, Aug 4, 2015 at 7:54 PM, Jonathan Haddad wrote:
> You're trying to solve a problem that doesn't exist. Cassandra only
> starts serving reads when it's ready.
>
> On Tue, Aug 4, 2015 at 10:51 AM horschi wro
You're trying to solve a problem that doesn't exist. Cassandra only starts
serving reads when it's ready.
On Tue, Aug 4, 2015 at 10:51 AM horschi wrote:
> Hi Robert,
>
> sorry for the confusion. Perhaps write_survey is not my solution
> (unfortunetaly I cant get it to work, so I dont really kno
Hi Robert,
sorry for the confusion. Perhaps write_survey is not my solution
(unfortunetaly I cant get it to work, so I dont really know). I just
thought that it *could* be my solution.
What I actually want:
I want to be able to start a new node, without it starting to serve reads
prematurely. I
:
> I had problems with write_survey.
>
> I opened a bug : https://issues.apache.org/jira/browse/CASSANDRA-9934
>
>
>
> *De :* horschi [mailto:hors...@gmail.com]
> *Envoyé :* mardi 4 août 2015 15:20
> *À :* user@cassandra.apache.org
> *Objet :* Re: auto_bootstrap=false brok
On Tue, Aug 4, 2015 at 6:19 AM, horschi wrote:
> I would like to separate these steps:
> 1. assign tokens
> 2. have the node in a joining state, so that I can copy in data
> 3. mark the node as ready
>
> Did anyone ever use write_survey for such a partial bootstrapping?
>
What you're asking do
I had problems with write_survey.
I opened a bug : https://issues.apache.org/jira/browse/CASSANDRA-9934
De : horschi [mailto:hors...@gmail.com]
Envoyé : mardi 4 août 2015 15:20
À : user@cassandra.apache.org
Objet : Re: auto_bootstrap=false broken?
Hi Paulo,
thanks for your feedback, but I
Hi Paulo,
thanks for your feedback, but I think this is not what I am looking for.
Starting with join_ring does not take any tokens in the ring. And the
"nodetool join" afterwards will again do token-selection and data loading
in one step.
I would like to separate these steps:
1. assign tokens
2
Hello Christian,
You may use the start-up parameter -Dcassandra.join_ring=false if you don't
want the node to join the ring on startup. More about this parameter here:
http://docs.datastax.com/en/cassandra/2.0/cassandra/tools/toolsCUtility_t.html
You can later join the ring via nodetool join comm
17 matches
Mail list logo
