Hello, Rajani Just a blind guess, it may recover dropped replicas to remaining nodes. Probably you need to request https://solr.apache.org/guide/solr/latest/deployment-guide/cluster-node-management.html#migratereplicas to remove replicas out of recycling node beforehand. WDYT?
On Wed, Sep 13, 2023 at 3:29 AM rajani m <rajinima...@gmail.com> wrote: > Hi Solr Users, > > Solr 9.1.1 version, upon restarting solr on any node in the cluster, a > unique event is triggered across all the *other* nodes in the cluster that > has an impact similar to restarting solr on all the other nodes in the > cluster. There is dip in the cpu usage, all the caches are emptied and > warmed up, there are disk reads/writes on all the other nodes. > > The nodes in the cluster are usually at 40% cpu usage and 80% memory, they > receive certain requests and updates, and at any time solr on a node is > restarted, the shards on that nodes take 1-2 minutes to recover and by the > time it is recovered, the other nodes receive an event that cause restart > like impact on them, seeing caches cleanup, cpu dip and so on. What can > cause this type of behavior? > > Thank you, > Rajani > -- Sincerely yours Mikhail Khludnev
