Setting auto_bootstrap on seed nodes is unnecessary and irrelevant. If the
node is a seed it will ignore auto_bootstrap and it *will not* bootstrap.
On 28 March 2018 at 15:49, Ali Hubail wrote:
> "it seems that we still need to keep bootstrap false?"
>
> Could you shed some
"it seems that we still need to keep bootstrap false?"
Could you shed some light on what would happen if the auto_bootstrap is
removed (or set to true as the default value) in the seed nodes of the
newly added DC?
What do you have in the seeds param of the new DC nodes (cassandra.
Date: Wed, Mar 28, 2018 10:48 AM
To: "user";
Subject: Re: auto_bootstrap for seed node
You might want to follow DataStax docs on this one:
For adding a DC to an existing cluster:
https://docs.datastax.com/en/dse/5.1/dse-admin/datastax_enterprise/operations/opsAddDCToCluster.htm
/datastax_enterprise/operations/opsAddNodeToCluster.html
briefly speaking,
adding one node to an existing cluster --> use auto_bootstrap
adding a DC to an existing cluster --> rebuild
You need to check the version of c* that you're running, and make sure you
pick the right doc version for that.
Dear All,
For adding a new DC ,we need to set auto_bootstrap: false and then run the
rebuild,finally we need to change auto_bootstrap: true,but for seed nodes,it
seems that we still need to keep bootstrap false?
Could anyone please confirm?
Thanks,
Peng Xiao
H and to make it serve reads only when it's
>> done. And to be more precise, we know when it's done and don't need it to
>> work by itself (automatically).
>>
> If you use auto_bootstrap=false in the same DC, then I think you are
> screwed. Afa
x27;d like to restart
> a node that need to deploy HH and to make it serve reads only when it's
> done. And to be more precise, we know when it's done and don't need it to
> work by itself (automatically).
>
If you use auto_bootstrap=false in the same DC, then I think you
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
at all, you told it not to bootstrap.
>
Let me correct myself. It should be: "its wrong because it isn't
bootstrapped". But that does not change what I am proposing: It still
should not serve reads.
‘auto_bootstrap’ is the knob that tells cassandra whether or not you want
>
You’re trying to force your view onto an established ecosystem. It’s not “wrong
only because its currently bootstrapping”, it’s not bootstrapping at all, you
told it not to bootstrap.
‘auto_bootstrap’ is the knob that tells cassandra whether or not you want to
stream data from other replicas
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
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
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
erve reads".
>
>
>
> Possible solutions so far:
>
> A) When starting a new node with auto_bootstrap=false, then I get a node
> that has no data, but serves reads. In my opinion it would be cleaner if it
> would stay in a joining state where it only receives writes.
>
>
want cassandra to wait for me to confirm "everything is ok,
now serve reads".
Possible solutions so far:
A) When starting a new node with auto_bootstrap=false, then I get a node
that has no data, but serves reads. In my opinion it would be cleaner if it
would stay in a joining stat
:
> 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
re:
> http://docs.datastax.com/en/cassandra/2.0/cassandra/tools/toolsCUtility_t.html
>
> You can later join the ring via nodetool join command:
> http://docs.datastax.com/en/cassandra/2.0/cassandra/tools/toolsJoin.html
>
> auto_bootstrap=false is typically used to bootstrap n
join command:
http://docs.datastax.com/en/cassandra/2.0/cassandra/tools/toolsJoin.html
auto_bootstrap=false is typically used to bootstrap new datacenters or
clusters, or nodes with data already on it before starting the process.
Cheers,
Paulo
2015-08-04 8:50 GMT-03:00 horschi :
> Hi everyone,
Hi everyone,
I'll just ask my question as provocative as possible ;-)
Isnt't auto_bootstrap=false broken the way it is currently implemented?
What currently happens:
New node starts with auto_bootstrap=false and it starts serving reads
immediately without having any data.
Would the
rry about a script accidentally provisioning new nodes.
>
auto_bootstrap is orthogonal to joining or not joining the ring.
https://engineering.eventbrite.com/changing-the-ip-address-of-a-cassandra-node-with-auto_bootstrapfalse/
Explains why. Basically joining a node without bootstrapping just mean
I'd consider solving your root problem of "people are starting and stopping
servers in prod accidentally" instead of making Cassandra more difficult to
manage operationally.
On Thu Dec 18 2014 at 4:04:34 AM Ryan Svihla wrote:
> why auto_bootstrap=false? The documentation
why auto_bootstrap=false? The documentation even suggests the opposite. If
you don't auto_bootstrap the node will take queries before it has copies of
all the data, and you'll get the wrong answer (it'd not be unlike using CL
ONE when you've got a bunch of dropped mutations on
- In Cassandra yaml set auto_bootstrap = false
- Boot node
- nodetool rebuild
Very similar to
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html
On 18 December 2014 at 14:04, Kevin Burton wrote:
>
> I’m trying to figure out th
I’m trying to figure out the best way to bootstrap our nodes.
I *think* I want our nodes to be manually bootstrapped. This way an admin
has to explicitly bring up the node in the cluster and I don’t have to
worry about a script accidentally provisioning new nodes.
The problem is HOW do you do it
On Thu, Jun 13, 2013 at 11:20 PM, Edward Capriolo wrote:
> CL.ONE requests for rows which do not exist are very fast.
>
> http://adrianotto.com/2010/08/dev-null-unlimited-scale/
>
Yep, /dev/null is a might force ;-)
I took a look at the YCSB source code and spotted the line of code
that caused o
't
> > fully understand what is going on, yet. The strategy works like this:
> > add new nodes to a Cassandra cluster with "auto_bootstrap = false" to
> > avoid streaming to the new nodes.
>
> If you set auto_bootstrap to false, new nodes take over responsibili
Jun 13, 2013 at 10:47 AM, Markus Klems wrote:
>> One scaling strategy seems interesting but we don't
>> fully understand what is going on, yet. The strategy works like this:
>> add new nodes to a Cassandra cluster with "auto_bootstrap = false" to
>&
On Thu, Jun 13, 2013 at 10:47 AM, Markus Klems wrote:
> One scaling strategy seems interesting but we don't
> fully understand what is going on, yet. The strategy works like this:
> add new nodes to a Cassandra cluster with "auto_bootstrap = false" to
> avoid streamin
this problem. One scaling strategy seems interesting but we don't
fully understand what is going on, yet. The strategy works like this:
add new nodes to a Cassandra cluster with "auto_bootstrap = false" to
avoid streaming to the new nodes. We were a bit surprised that this
st
I can't explain the technical reason why it's not advisable to bootstrap a
seed. However, from what I've read you would bootstrap the node as a non-seed
first, then add it as seed once it has finished bootstrapping.
On Apr 8, 2011, at 9:30 PM, mcasandra wrote:
> in yaml:
> # Set to true to ma
in yaml:
# Set to true to make new [non-seed] nodes automatically migrate data
# to themselves from the pre-existing nodes in the cluster.
Why only non-seed nodes? What if seed nodes need to bootstrap?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble
, Maki Watanabe wrote:
>
> Hello,
> According to the Wiki/StorageConfiguration page, auto_bootstrap is
> described as below:
>
> auto_bootstrap
> Set to 'true' to make new [non-seed] nodes automatically migrate the
> right data to themselves. (If no InitialToken
e Wiki/StorageConfiguration page, auto_bootstrap is
> described as below:
>
> auto_bootstrap
> Set to 'true' to make new [non-seed] nodes automatically migrate the
> right data to themselves. (If no InitialToken is specified, they will
> pick one such that they will get
Hello,
According to the Wiki/StorageConfiguration page, auto_bootstrap is
described as below:
auto_bootstrap
Set to 'true' to make new [non-seed] nodes automatically migrate the
right data to themselves. (If no InitialToken is specified, they will
pick one such that they will ge
38 matches
Mail list logo
