[
https://issues.apache.org/jira/browse/IMPALA-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962625#comment-16962625
]
ASF subversion and git services commented on IMPALA-9026:
---------------------------------------------------------
Commit 41426077fb0e4c67c954801220b1a8296de5ff4a in impala's branch
refs/heads/master from Michael Ho
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=4142607 ]
IMPALA-9026: Use resolved IP address for statestore subscriber
This change adds a flag (--statestore_subscriber_use_resolved_address)
which, if set to true, allows statestore subscribers to use its
resolved IP address instead of its hostname as the heartbeat
address which statestore sends heartbeats / updates to.
This flag is useful in certain situation in which the subscriber's
DNS entry may not be present for a valid reason (e.g. a Kubernetes
pod whose readiness probe returns false). An example is that there
are multiple Impala coordinators but only one of them will be active
at a time (for admission control reason) and the rest will serve
as backup. In which case, we still want the backup coordinators to
receive updates from statestore but not serve any queries.
Change-Id: Ieb8302dec0e52beb9f0b88306a51c38ff42a63a2
Reviewed-on: http://gerrit.cloudera.org:8080/14388
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Add an option to use resolved IP address for Statestore subscriber
> ------------------------------------------------------------------
>
> Key: IMPALA-9026
> URL: https://issues.apache.org/jira/browse/IMPALA-9026
> Project: IMPALA
> Issue Type: Improvement
> Components: Distributed Exec
> Affects Versions: Impala 3.4.0
> Reporter: Michael Ho
> Assignee: Michael Ho
> Priority: Minor
>
> Currently, statestore subscribers currently register with statestore using
> their hostnames. There may be certain deployment scenarios in which a pod may
> have an IP address but its DNS entry is not available for a valid reason
> (e.g. a Kubernetes pod whose readiness probe returns false). An example could
> be that there could be more than one instances of an Impala component (e.g.
> coordinator) but only one of them will be active at a time and the rest will
> serve as backup. In which case, we still want the backup coordinator to
> receive any updates from statestore but not serve any queries until the
> primary coordinator fails.
> To handle the case above, we may allow statestore subscribers to register
> with statestore using its IP address instead of hostname. This may not work
> with some existing secure deployment in which TLS is enabled between Impala
> hosts as there may be mismatch between the hostname used at Thrift layer and
> the certificate so this option is disabled by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
