About solr restart

[苗海泉 <ms...@gmail.com>]

We found a problem in the solr6.0 version. After solr restarts data
recovery on the zookeeper, the solr collection configuration will be
centralized in the clusterstate.json file. If the number of clusters and
replicas is a bit more, it is very easy to exceed 1M. Has caused a series
of problems such as the inability to read the data on Zookeepe. Did someone
have a good solution, thank you!

-- 
==============================
联创科技
知行如一
==============================
[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
18/06/25
上午9:43:21

Re: About solr restart

[Erick Erickson <er...@gmail.com>]

For quite some time, collection information has been stored in
individual state.json nodes, not clusterstate.json. See the
MIGRATESTATEFORMAT Collections API call.

How many collections and replicas do you have all told?

Best,
Erick

On Sun, Jun 24, 2018 at 6:43 PM, 苗海泉 <ms...@gmail.com> wrote:
> We found a problem in the solr6.0 version. After solr restarts data
> recovery on the zookeeper, the solr collection configuration will be
> centralized in the clusterstate.json file. If the number of clusters and
> replicas is a bit more, it is very easy to exceed 1M. Has caused a series
> of problems such as the inability to read the data on Zookeepe. Did someone
> have a good solution, thank you!
>
> --
> ==============================
> 联创科技
> 知行如一
> ==============================
> [image: Mailtrack]
> <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
> Sender
> notified by
> Mailtrack
> <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
> 18/06/25
> 上午9:43:21