[
https://issues.apache.org/jira/browse/SOLR-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257055#comment-16257055
]
Erick Erickson commented on SOLR-11656:
---------------------------------------
I'll take a look over the weekend. Meanwhile I'd note that the whole
REBALANCELEADER functionality is only there for extreme cases (i.e. 100+ of
leaders happened to land on the same node). The additional burden of being a
leader is pretty miminal, to the point of being hard to measure if there just a
few leaders on a particular node.
This is still a bug, thanks for bringing it up and providing a patch. I'm just
suggesting you may just be better off avoiding REBALANCELEADERS altogether, but
then I don't know your setup so it may indeed be beneficial.
> TLOG replication doesn't work properly after rebalancing leaders.
> -----------------------------------------------------------------
>
> Key: SOLR-11656
> URL: https://issues.apache.org/jira/browse/SOLR-11656
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: replication (java)
> Affects Versions: 7.1
> Reporter: Yuki Yano
> Attachments: SOLR-11656.patch
>
>
> With TLOG replica type, the replication may stop after invoking rebalance
> leaders API.
> This can be reproduced by following steps:
> # Create SolrCloud with TLOG replica type.
> # Set perferredleader flag to some of no-leader nodes.
> # Invoke rebalance leaders API.
> # The replication stops in nodes which were "leader" before rebalancing.
> Because the leader node doesn't have the replication thread, we need to
> create it when the status is changed from "leader" to "replica". On the other
> hand, rebalance leaders API doesn't consider this matter, and the replication
> may stop if the status is changed from "leader" to "replica" by rebalance
> leaders.
> Note that, we can avoid this problem if we reload or restart Solr after
> rebalancing leaders.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
