This is a followup to my last question with my findings thus far. In a scenario where there is one SolrCloud resource per-shard I'm seeing the overseer node get skipped entirely during rolling restarts. So, it appears the solr-operator can only manage rolling restarts when there is one SolrCloud object in the cluster.
Joel Bernstein http://joelsolr.blogspot.com/ On Tue, Oct 12, 2021 at 6:44 PM Joel Bernstein <[email protected]> wrote: > Hi, > > I saw that the Solr operator takes into account collection topology when > performing rolling restarts. In a situation where there is one SolrCloud > object per-shard, I'm wondering how this will behave. In this case the Solr > Operator would receive a different CR for each shard which would kick off > the rolling restarts in parallel. Would the operator be able to understand > that it was operating on a single shard in each CR and not get tangled up > in the larger cluster state? > > Thanks, > Joel > > >
