[
https://issues.apache.org/jira/browse/IMPALA-13208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866922#comment-17866922
]
Quanlong Huang commented on IMPALA-13208:
-----------------------------------------
To start a new cluster in the dev env using the existing catalogd and
statestore, use commands like this:
{code}
bin/start-impala-cluster.py --add_impalads --impalad_args=--cluster_id=cluster3
--cluster_size=3{code}
> Add cluster id to the membership and request-queue topic names
> --------------------------------------------------------------
>
> Key: IMPALA-13208
> URL: https://issues.apache.org/jira/browse/IMPALA-13208
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend
> Reporter: Quanlong Huang
> Assignee: Quanlong Huang
> Priority: Critical
> Fix For: Impala 4.5.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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]