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

Posted to issues-all@impala.apache.org by "Lars Volker (JIRA)" <ji...@apache.org> on 2019/04/26 01:28:00 UTC

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

Lars Volker created IMPALA-8460:
-----------------------------------

             Summary: Unify cluster membership management in the backend
                 Key: IMPALA-8460
                 URL: https://issues.apache.org/jira/browse/IMPALA-8460
             Project: IMPALA
          Issue Type: Bug
          Components: Backend
    Affects Versions: Impala 3.3.0
            Reporter: Lars Volker
            Assignee: Lars Volker


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)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org