[jira] [Commented] (SOLR-17204) REPLACENODE command does not support source not being live
[ 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 (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
[jira] [Resolved] (SOLR-17204) REPLACENODE command does not support source not being live
[ 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
[jira] [Commented] (SOLR-17204) REPLACENODE command does not support source not being live
[ https://issues.apache.org/jira/browse/SOLR-17204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837053#comment-17837053 ] ASF subversion and git services commented on SOLR-17204: Commit c3c83ffb8dba17dd79f78429df65869d1b7d87bb in solr's branch refs/heads/main from Vincent Primault [ https://gitbox.apache.org/repos/asf?p=solr.git;h=c3c83ffb8db ] 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 > 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
Re: [PR] SOLR-17204: REPLACENODE supports the source node not being live [solr]
dsmiley merged PR #2353: URL: https://github.com/apache/solr/pull/2353 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-17204) REPLACENODE command does not support source not being live
[ https://issues.apache.org/jira/browse/SOLR-17204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated SOLR-17204: Issue Type: Improvement (was: Bug) > 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: 20m > 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
