lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-11067) REPLACENODE should make it optional to provide a target node
Date Tue, 27 Feb 2018 00:01:00 GMT


ASF subversion and git services commented on SOLR-11067:

Commit 1fc3ca0cbb2fcdd99c4a58dcf98d346e1bab5015 in lucene-solr's branch refs/heads/master
from noble
[;h=1fc3ca0 ]

SOLR-11067: AwaitsFix. The test fails often as the target node some times is same as the source

> REPLACENODE should make it optional to provide a target node
> ------------------------------------------------------------
>                 Key: SOLR-11067
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling, SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Noble Paul
>            Priority: Major
>             Fix For: master (8.0), 7.3
>         Attachments: SOLR-11067.patch
> The REPLACENODE API currently accepts a replacement target and moves all replicas from
the source to the given target. We can improve this by having it figure out the right target
node for each replica contained in the source.
> This can also then be a thin wrapper over nodeLost event just like how UTILIZENODE (SOLR-9743)
can be a wrapper over nodeAdded event.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message