[
https://issues.apache.org/jira/browse/IMPALA-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823754#comment-17823754
]
Wenzhe Zhou commented on IMPALA-12868:
--------------------------------------
Checked the flagfile for impala daemons. Two flags for statestore HA are not
specified in the flagfile of impala-statetstore - "state_store_ha_port" and
"state_store_peer_host". "state_store_ha_port" is used by statestore, it's not
necessary to be set in the flagfiles of catalog and coordinator.
The flagfiles of two statestore daemons should have different values for
"state_store_peer_host", which point to its peer host, e.g.
"state_store_peer_host=statestored-0" for statestored-1,
"state_store_peer_host=statestored-1" for statestored-0.
> Catalogd's statestore subscriber gets stuck in a loop trying to process
> UpdateCatalogd RPC
> ------------------------------------------------------------------------------------------
>
> Key: IMPALA-12868
> URL: https://issues.apache.org/jira/browse/IMPALA-12868
> Project: IMPALA
> Issue Type: Task
> Reporter: Anubhav Jindal
> Assignee: Wenzhe Zhou
> Priority: Critical
> Attachments: Screenshot 2024-03-04 at 3.21.55 PM.png
>
>
> When Impala is running with statestore HA and catalog HA enabled, the below
> log statement in both catalogd instances is printed about 9 times each second:
> {code:java}
> I0304 22:27:28.446938 289 statestore-subscriber.cc:421] Skipped updating
> catalogd message from unknown or inactive statestored:
> f4439d6fdb0ec572:87102dd6c845dab7{code}
> On restarting catalogDs, the log statements are not observed.
> STR:
> # Create Impala with both catalogD HA and statestoreD HA
> # Check catalogD container logs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
