[
https://issues.apache.org/jira/browse/SOLR-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132100#comment-18132100
]
Nick Shanin commented on SOLR-8553:
-----------------------------------
>From code reading against apache/main b73f03976fa, RELOAD is sent only to
>ACTIVE replicas
>(solr/core/src/java/org/apache/solr/cloud/api/collections/CollApiCmds.java:277).
> A candidate is to include RECOVERING replicas too, so a schema change reaches
>them. Is this still a problem?
🤖 AI-generated 🤖
> Schema API could skip updating recovering replicas
> --------------------------------------------------
>
> Key: SOLR-8553
> URL: https://issues.apache.org/jira/browse/SOLR-8553
> Project: Solr
> Issue Type: Bug
> Reporter: Varun Thacker
> Priority: Major
>
> I was looking a OverseerCollectionMessageHandler#RELOAD and the code only
> reloads those replicas which are in active state:
> {code}
> collectionCmd(message, params, results, Replica.State.ACTIVE, asyncId,
> requestMap);
> {code}
> I don't know the schema and config api's well enough but say we sent a
> command while one of the replicas was recovering , that replica would not get
> updated right?
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
