You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Lars Volker (JIRA)" <ji...@apache.org> on 2019/06/03 20:33:00 UTC

[jira] [Resolved] (IMPALA-8460) Unify cluster membership management in the backend

     [ https://issues.apache.org/jira/browse/IMPALA-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Volker resolved IMPALA-8460.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.3.0

> Unify cluster membership management in the backend
> --------------------------------------------------
>
>                 Key: IMPALA-8460
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8460
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 3.3.0
>            Reporter: Lars Volker
>            Assignee: Lars Volker
>            Priority: Major
>             Fix For: Impala 3.3.0
>
>
> We currently subscribe to the cluster-membership statestore topic in both the ImpalaServer and the Scheduler. Updates are then also propagated to the Frontend. Additionally the Scheduler has its own representation of the local backend descriptor, which is not kept in sync with the one in the Impala server.
> To make cluster-membership and the interactions with the statestore easier to reason about, we should pull all membership handling in to a single place.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)