[
https://issues.apache.org/jira/browse/SOLR-14276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski resolved SOLR-14276.
------------------------------------
Resolution: Invalid
Hi Jason,
As a community we use the JIRA bugtracker for known or suspected bugs (ideally
with steps for reproduction).
Since this is more of a question or request for help, your questions are better
off directed at the solr-user mailing list ([email protected]).
That's also much more widely read, so posting there isn't just to satisfy our
arbitrary rules - it's also where you're much more likely to get an answer to
your question. See
[here|https://lucene.apache.org/solr/community.html#mailing-lists-irc] for
information about subscribing or posting to our mailing lists.
> At various times when we restart Solr or following a hard reboot, Solr
> generates multiple replicas beyond the defined amount
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-14276
> URL: https://issues.apache.org/jira/browse/SOLR-14276
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.2.1
> Reporter: Jason Randall
> Priority: Major
>
> Our cluster is set up so that each daily log shard has 3 replicas. It should
> create one replica for each of the sites in the cluster and then host one of
> the replicas on each site. We have days in which we get only 1 or 2 replicas
> instead of 3. We have days in which we get multiple replicas. The replicas
> are often randomly dispersed amongst the nodes in the cluster. So we might
> have 5 hosted on node 2 and 3 on node 3 but maybe none on node 1 for that
> day. Can you provide possible scenarios as to why this may happen? And how to
> resolve the issue?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]