[
https://issues.apache.org/jira/browse/SOLR-17204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-17204.
---------------------------------
Fix Version/s: 9.6.0
Resolution: Fixed
I reclassified this as an improvement because I think a user will mostly
perceive it this way.
Thanks for contributing Vincent!
> REPLACENODE command does not support source not being live
> ----------------------------------------------------------
>
> Key: SOLR-17204
> URL: https://issues.apache.org/jira/browse/SOLR-17204
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Vincent Primault
> Priority: Minor
> Fix For: 9.6.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The REPLACENODE command explicitly does not support the source node not being
> live, and fails at the beginning if it is not live. However, later on, it
> also explicitly supports that same source node not being live.
> In most situations, except if a shard has a single replica being on the down
> source node, the unavailability of the source node should not be problematic.
> I therefore propose to support running the REPLACENODE command with the
> source node not being live.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
