[
https://issues.apache.org/jira/browse/CASSANDRA-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926513#action_12926513
]
Jonathan Ellis commented on CASSANDRA-1683:
-------------------------------------------
bq. I didn't know we were discouraging this.
We definitely are. The only time autobootstrap should be off is when you're
bringing up your initial cluster.
bq. If we are, the right thing to do is size the data directories and throw a
fatal error on startup if there are no data files and autobootstrap is off.
I don't follow. The situation we need to guard against is "someone forgot to
set autobootstrap=true when adding a new node to the cluster after it already
has data in it," checking size of data dir will catch that but it will also
false positive on the initial cluster scenario.
> Bootstrapped node (autobootstrap==false) starts receiving writes before
> schema is propagated.
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1683
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1683
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 1
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Fix For: 0.7.0
>
> Attachments:
> v2-0001-non-bootstrap-nodes-wait-for-schema-propagation.txt
>
>
> This is what generates the
> {code}org.apache.cassandra.db.UnserializableColumnFamilyException: Couldn't
> find cfId=1016{code} errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
