lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-7431) stateFormat=2 is not respected when collections are recreated.
Date Mon, 20 Apr 2015 18:38:58 GMT
Erick Erickson created SOLR-7431:
------------------------------------

             Summary: stateFormat=2 is not respected when collections are recreated.
                 Key: SOLR-7431
                 URL: https://issues.apache.org/jira/browse/SOLR-7431
             Project: Solr
          Issue Type: Bug
    Affects Versions: 5.1
            Reporter: Erick Erickson


The following steps produce a clusterstate.json at the root of the Solr hive in ZK rather
than a state.json node under the collection.

0> Start separate ZK locally
1> create a collection with stock 5.x
2> shut down all solr nodes and Zookeeper
3> rm -rf /tmp/zookeeper
4> start ZK
5> upconfig your configuration
6> start the solr nodes.

When I created the nodes originally, the collection had a state.json node below it, but after
the above there was only the uber-clusterstate.json node and no state.json below the collection.

Even in this state, new collections have the state.json as a child of the collection.

I'm not quite sure what happens if you do something less drastic than blow the entire ZK configuration
away. Say you remove just one replica's information from the ZK state, it's not clear to me
where it gets re-added.

Of course this is not something that's very common, I ran in to it trying to hack an upgrade
from 4.x to 5.x and migrate from the single clusterstate.json to state-per-collection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message