[
https://issues.apache.org/jira/browse/SOLR-17204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837055#comment-17837055
]
ASF subversion and git services commented on SOLR-17204:
--------------------------------------------------------
Commit d23658db2e54f1c5ef56511b169ad738419acd78 in solr's branch
refs/heads/branch_9x from Vincent Primault
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=d23658db2e5 ]
SOLR-17204: REPLACENODE supports the source node not being live (#2353)
The REPLACENODE command now supports the source not being live
Co-authored-by: Vincent Primault <vprima...@salesforce.com>
(cherry picked from commit c3c83ffb8dba17dd79f78429df65869d1b7d87bb)
> 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
> 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
