hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <>
Subject [jira] [Commented] (HIVE-12568) Provide an option to specify network interface used by Spark remote client [Spark Branch]
Date Thu, 28 Jan 2016 10:34:40 GMT


Lefty Leverenz commented on HIVE-12568:

HIVE-12940 merged this to master for release 2.1.0, so I added a TODOC2.1 label.

Ping for the doc question:  Should *hive.spark.client.rpc.server.address* be mentioned in
Hive on Spark: Getting Started?

> Provide an option to specify network interface used by Spark remote client [Spark Branch]
> -----------------------------------------------------------------------------------------
>                 Key: HIVE-12568
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Spark
>    Affects Versions: 1.1.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>              Labels: TODOC-SPARK, TODOC2.1
>             Fix For: spark-branch
>         Attachments: HIVE-12568.0-spark.patch, HIVE-12568.1-spark.patch, HIVE-12568.2-spark.patch,
> Spark client sends a pair of host name and port number to the remote driver so that the
driver can connects back to HS2 where the user session is. Spark client has its own way determining
the host name, and pick one network interface if the host happens to have multiple network
interfaces. This can be problematic. For that, there is parameter, hive.spark.client.server.address,
which user can pick an interface. Unfortunately, this interface isn't exposed.
> Instead of exposing this parameter, we can use the same logic as Hive in determining
the host name. Therefore, the remote driver connecting to HS2 using the same network interface
as a HS2 client would do.
> There might be a case where user may want the remote driver to use a different network.
This is rare if at all. Thus, for now it should be sufficient to use the same network interface.

This message was sent by Atlassian JIRA

View raw message