[
https://issues.apache.org/jira/browse/CASSANDRA-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426732#comment-13426732
]
Chris Lohfink commented on CASSANDRA-4465:
------------------------------------------
I have also seen this on a 7 node (Ubuntu 10.04 in Rackspace, and 10.04 in ESX
cluster) cluster. In fact this has happened to me often. I have seen it when
I have created a new column family (wait for schema agreement) then add the
index (via solr schema.xml http post) but I cannot reproduce on single node
cluster.
> Index fails to be created on all nodes in cluster, restart resolves
> -------------------------------------------------------------------
>
> Key: CASSANDRA-4465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4465
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.10
> Environment: 21 node cluster, Ubuntu Linux 11.10 in a virtualized
> environment, Apache cassandra community release, binary distribution
> Reporter: Grant Heffernan
> Priority: Minor
>
> On a production cluster, under load, creating an index on a column resulted
> in the index being successfully created on 4 of 21 nodes. All nodes received
> the schema agreement and were in concert. There were no errors logged on any
> of the nodes that failed to build the index.
> A rolling restart of the cluster resulted in the nodes which had previously
> failed to build the index doing so when coming back up from a restart.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
