[
https://issues.apache.org/jira/browse/SOLR-15795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444830#comment-17444830
]
ASF subversion and git services commented on SOLR-15795:
--------------------------------------------------------
Commit 7cd45b750d4f7b1ae360e83fdf74a5f6ae183eaf in lucene-solr's branch
refs/heads/branch_8_11 from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=7cd45b7 ]
SOLR-15795: Fix REPLACENODE to not use source node (#414)
> REPLACENODE does not check that target node is different from source node
> -------------------------------------------------------------------------
>
> Key: SOLR-15795
> URL: https://issues.apache.org/jira/browse/SOLR-15795
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 7.3, 8.0
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> As of SOLR-11067, the REPLACENODE API is able to select a new node for you if
> you do not provide one yourself, via the {{target}} parameter.
> However, there is nothing done to guarantee that the new node selected for
> you is different from the original node. It looks like [~hossman] made this
> observation in the original JIRA, but I'm not sure any fixes were made.
> I propose, similarly to [~hossman] did, that the API should also throw an
> error in case there is no other live node to send the replicas to.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
