[
https://issues.apache.org/jira/browse/IMPALA-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933962#comment-17933962
]
ASF subversion and git services commented on IMPALA-13259:
----------------------------------------------------------
Commit a07bf84caeae5c2db9dc862cccd620c4295b8325 in impala's branch
refs/heads/master from m-sanjana19
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=a07bf84ca ]
IMPALA-13259: [DOCS] Documentation for adding cluster id to the
membership and request-queue topic names
This update documents the use of the cluster ID for membership
and request queue topics based on its implementation in
Impala’s statestore and query scheduling mechanisms.
Change-Id: I7f124491fe7b172afc7a524f88001498721a0234
Reviewed-on: http://gerrit.cloudera.org:8080/22601
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Quanlong Huang <[email protected]>
> [DOC] Coordinators' Subscription to Statestore Topics- impala-membership and
> impala-request-queue
> -------------------------------------------------------------------------------------------------
>
> Key: IMPALA-13259
> URL: https://issues.apache.org/jira/browse/IMPALA-13259
> Project: IMPALA
> Issue Type: Documentation
> Reporter: Sanjana Malhotra
> Assignee: Sanjana Malhotra
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> Coordinators subscribe to 3 statestore topics: catalog-update,
> impala-membership and impala-request-queue. The last two topics are about
> query scheduling. To separate the cluster or share catalogd and statestore
> across Impala clusters, we can add the cluster id to these two topic names.
> Impalads are only visible to each other inside the same cluster (i.e. using
> the same cluster id). Queries won't be scheduled across clusters.
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
