You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Sahil Takiar (Jira)" <ji...@apache.org> on 2020/02/06 20:30:00 UTC
[jira] [Resolved] (IMPALA-9342) Membership updates should only
remove quiescing nodes from the blacklist
[ https://issues.apache.org/jira/browse/IMPALA-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sahil Takiar resolved IMPALA-9342.
----------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Membership updates should only remove quiescing nodes from the blacklist
> ------------------------------------------------------------------------
>
> Key: IMPALA-9342
> URL: https://issues.apache.org/jira/browse/IMPALA-9342
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
> Fix For: Impala 3.4.0
>
>
> {{ClusterMembershipMgr::UpdateMembership}} will remove a node from the blacklist (if it is on the blacklist) if the method receives an update from the Statestore about the node. Currently, the Statestore *should* only send an update about the node if the node starts quiescing. If a node starts quiescing, it should be removed from the blacklist since it quiescing nodes aren't part of any executor groups anyway (no queries should be scheduled on them).
> After running some experiments locally, it seems there are some other cases where the Statestore sends the {{ClusterMembershipMgr}} an update about a node even if it's quiescing state has not changed. Unfortunately, I haven't been able to fully track down what is triggering this, so far it only happens on cluster start up.
> The {{ClusterMembershipMgr}} should only un-blacklist a node if that node is quiescing, currently it un-blacklists a node on any update to the node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)