[
https://issues.apache.org/jira/browse/IMPALA-7985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745636#comment-16745636
]
Andrew Sherman commented on IMPALA-7985:
----------------------------------------
OK so the proposal is to make an incompatible change to use the kprc_port.
The common case of specifying a host only will use the krpc_port of the
coordinator from FLAGS_krpc_port which will allow shutdown of an impalad that
has left the cluster.
Using the krpc_port will mean a docs change.
The only question then is whether it is confusing for a user who wants to find
the krpc_port. If they list /backends in the webui they will see
host:thrift_port which they might reasonably expect to be able to use when
naming an impalad. Do we want to add host:krpc_port to the /backends output?
Are there other places that this is needed?
> Port RemoteShutdown() to KRPC
> -----------------------------
>
> Key: IMPALA-7985
> URL: https://issues.apache.org/jira/browse/IMPALA-7985
> Project: IMPALA
> Issue Type: Sub-task
> Components: Distributed Exec
> Affects Versions: Impala 3.1.0
> Reporter: Michael Ho
> Assignee: Andrew Sherman
> Priority: Major
> Labels: ramp-up
>
> Port RemoteShutdown() to KRPC. It's currently implemented as Thrift RPC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
