Hi Aeljami, thanks for the ticket. I'll keep an eye on it.
I can't get the survey to work at all on 2.0 (I am not getting any schema on the survey node). So I guess the survey is not going to be a solution for now. kind regards, Christian On Tue, Aug 4, 2015 at 3:29 PM, <aeljami....@orange.com> wrote: > 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 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. have the node in a joining state, so that I can copy in data > > 3. mark the node as ready > > > > > > I just saw that perhaps write_survey could be misused for that. > > > > Did anyone ever use write_survey for such a partial bootstrapping? > > Do I have to worry about data-loss when using multiple write_survey nodes > in one cluster? > > > > kind regards, > > Christian > > > > > > > > On Tue, Aug 4, 2015 at 2:24 PM, Paulo Motta <pauloricard...@gmail.com> > wrote: > > 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 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 <hors...@gmail.com>: > > 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 following be more correct: > > - New node should stay in a joining state > > - Operator loads data (e.g. using nodetool rebuild or putting in backupped > files or whatever) > > - Operator has to manually switch from joining into normal state using > nodetool (only then it will start serving reads) > > > > Wouldn't this behaviour more consistent? > > > > kind regards, > > Christian > > > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > >
