[
https://issues.apache.org/jira/browse/SOLR-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724029#comment-17724029
]
Houston Putman commented on SOLR-16806:
---------------------------------------
{quote}Surely you don't mean that; one could move them one by one. That is "a
way". Maybe not convenient, and there is a desire for balancing
sophistication/rules, and that's your point.
{quote}
Yeah I mean that there is no way to populate a new node without choosing the
replicas yourself. I can update the text to make this more clear.
{quote}Why HTTP {*}PUT{*}; is it JSON that is subsequently retrievable? If so
then I could understand. If it's a command (as it looks because the path looks
like a verb), then *POST* would be a better choice IMO.
{quote}
I don't really have a strong opinion here. I'm fine using a POST instead. The
HTTP verbs don't really address a lot of our use cases very well IMO.
> Add a BalanceReplicas API
> -------------------------
>
> Key: SOLR-16806
> URL: https://issues.apache.org/jira/browse/SOLR-16806
> Project: Solr
> Issue Type: Sub-task
> Reporter: Houston Putman
> Priority: Major
>
> Currently there is no way to move replicas to a new, empty, Solr node. The
> logic we would need for this is to choose the best replicas to move to an
> empty Solr node, and stop when that Solr node matches the rest of the cluster.
> This logic is very close to merely balancing the existing replicas across a
> given set of nodes. So instead of creating a similar command that solves a
> subset of use-cases, it is probably worth it to take a bit more effort and
> create the general balance-replicas API to solve all balancing use-cases.
> The API would be quite simple. It would be something like {*}PUT
> "/api/cluster/balanceReplicas"{*}, and it would take in a list of nodes:
> {"nodes": [ "node1", "node2" ]}
> If no nodes were provided in the request body, then Solr would default to
> balancing across all data nodes.
> I don't see a need to write a V1 API for this.
> This requires adding method signatures to the PlacementPlugin, but we can
> make them default to a NO-OP, preserving compatibility for existing
> custom-plugins.
--
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
