On 1/4/2017 6:23 AM, Hendrik Haddorp wrote:
> Problem is that we would like to run without down times. Rolling
> updates worked fine so far except when creating a collection at the
> wrong time. I just did another test with stateFormat=2. This seems to
> greatly improve the situation. One collectio
Problem is that we would like to run without down times. Rolling updates
worked fine so far except when creating a collection at the wrong time.
I just did another test with stateFormat=2. This seems to greatly
improve the situation. One collection creation got stuck but other
creations still w
NOTE: Your problem is perfectly valid, this is something of a
side issue.
You shouldn't have a clusterstate.json in 6x. Or 5x either for
that matter. More accurately it will be at most an empty node.
instead, each collection should have a "state.json" file. There
are a couple of reasons for this:
On 1/3/2017 2:59 AM, Hendrik Haddorp wrote:
> I have a SolrCloud setup with 5 nodes and am creating collections with
> a replication factor of 3. If I kill and restart nodes at the "right"
> time during the creation process the creation seems to get stuck.
> Collection data is left in the clusterst
Hi,
I have a SolrCloud setup with 5 nodes and am creating collections with a
replication factor of 3. If I kill and restart nodes at the "right" time
during the creation process the creation seems to get stuck. Collection
data is left in the clusterstate.json file in ZooKeeper and no
collecti
