>From what I know until today, the status of a solr cluster used to be stored in a zk entry /clusterstate.json; but is now, from solr 5.0, stored within a sub-folder /collections/<xxx>/state.json.
We are having issues with our cluster, and I have noticed today that: for most of the collections there is a /state.json entry within /collections/<xxxx>/state.json but for some of them there is no entry state.json. On the other hand, there is a /clusterstate.json; which I would have not expected. What is going on? Who decides where the state of a collection is written to? Can I force it somehow? Because, from what I can understand, we're facing the 'few hundreds collections' issue I've read about some time ago. Let me explain: Just a few figures: - we currently have 103 collections - most of them have 40 shards and 2 replicas each Which brings to approx 800 replicas in total. Now, we had found references somewhere on the net saying that the 'number of collections' of a solr cluster should remain within the 'few hundreds' range. because of performance issue. Since each 'collection' would point to the same zk entry. Comment seemed to be bound to solr 4, though. But now, we have reached 800 nodes. Which shouldn't be a problem if they cluster in groups of 80 nodes at a time (1 collection). But is definitely an issue if they all point to a single zk node. Thanks already for any hint at where to look Patrick
