[
https://issues.apache.org/jira/browse/CASSANDRA-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926416#action_12926416
]
Jonathan Ellis commented on CASSANDRA-1683:
-------------------------------------------
bq. The only thing I don't like about this approach, is that it forces the
first seed on a single node cluster (the first node) to block for a schema
before serving reads.
Should we cap it at our standard "I should have heard from someone by now if
there was someone to hear from" 30s time in case someone wants to do something
weird like query the system tables?
nit: 100ms feels like a better busywait time, i'd like "serving reads" to
appear instantaneous to a human who just created his first keyspace from the cli
> 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:
> v1-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.
