Solr doesn’t scale very well with ~2K collections, and yes de bottleneck is Zookeeper itself.
Zookeeper doesn’t perform operation as quickly as expected with folders with a lot of children. In a scenario where you are in a recovery state (a node crash), this limitation will hurt a lot, the queue work stacks recovery operations due the low throughput to consume the queue. Regards. -- Yago Riveiro On 29 Jun 2018 17:38 +0100, Bertrand Mahé <bm...@servicepilot.com>, wrote: > Hi, > > > > In order to store timeseries data and perform deletion easily, we create a > several collections per day and then use aliases. > > > > We are using SOLR 7.3 and we have 2 questions: > > > > Q1 : In order to access quickly the latest data would it be possible to load > cores in descending chronological order rather than alphabetical order? > > > > Q2: When we exceed 1200-1300 collections, zookeeper suddenly changes from > 6-700 KB RAM to 3 GB RAM which makes zoo very slow or almost unusable. Is > this normal? > > > > Thanks in advance, > > > > Bertrand >
