Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 17 Mar 2017 01:57:41 +0000 (UTC)
From: "Chaoyu Tang (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13047177.1488339716000.45105.1489715861642@Atlassian.JIRA>
In-Reply-To: <JIRA.13047177.1488339716000@Atlassian.JIRA>
References: <JIRA.13047177.1488339716000@Atlassian.JIRA> <JIRA.13047177.1488339716451@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HIVE-16071) Spark remote driver misuses the
 timeout in RPC handshake
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 17 Mar 2017 01:57:52 -0000


     [ https://issues.apache.org/jira/browse/HIVE-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chaoyu Tang updated HIVE-16071:
-------------------------------
    Attachment: HIVE-16071.patch

Change to use the hive.spark.client.connect.timeout value for sasl handshake timeout  (cancelTask) at RpcServer side. [~xuefuz], [~lirui], could you review it? Thanks.
In addition, I am thinking about renaming the property hive.spark.client.connect.timeout and 
hive.spark.client.server.connect.timeout to hive.spark.rpc.sasl.handshake.timeout and hive.spark.remote.driver.register.timeout respectively. The rename should be tracked in a separate JIRA since we need consider property name backward compatibility issue. Comments?

> Spark remote driver misuses the timeout in RPC handshake
> --------------------------------------------------------
>
>                 Key: HIVE-16071
>                 URL: https://issues.apache.org/jira/browse/HIVE-16071
>             Project: Hive
>          Issue Type: Bug
>          Components: Spark
>            Reporter: Chaoyu Tang
>            Assignee: Chaoyu Tang
>         Attachments: HIVE-16071.patch, HIVE-16071.patch
>
>
> Based on its property description in HiveConf and the comments in HIVE-12650 (https://issues.apache.org/jira/browse/HIVE-12650?focusedCommentId=15128979&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15128979), hive.spark.client.connect.timeout is the timeout when the spark remote driver makes a socket connection (channel) to RPC server. But currently it is also used by the remote driver for RPC client/server handshaking, which is not right. Instead, hive.spark.client.server.connect.timeout should be used and it has already been used by the RPCServer in the handshaking.
> The error like following is usually caused by this issue, since the default hive.spark.client.connect.timeout value (1000ms) used by remote driver for handshaking is a little too short.
> {code}
> 17/02/20 08:46:08 ERROR yarn.ApplicationMaster: User class threw exception: java.util.concurrent.ExecutionException: javax.security.sasl.SaslException: Client closed before SASL negotiation finished.
> java.util.concurrent.ExecutionException: javax.security.sasl.SaslException: Client closed before SASL negotiation finished.
>         at io.netty.util.concurrent.AbstractFuture.get(AbstractFuture.java:37)
>         at org.apache.hive.spark.client.RemoteDriver.<init>(RemoteDriver.java:156)
>         at org.apache.hive.spark.client.RemoteDriver.main(RemoteDriver.java:556)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:606)
>         at org.apache.spark.deploy.yarn.ApplicationMaster$$anon$2.run(ApplicationMaster.scala:542)
> Caused by: javax.security.sasl.SaslException: Client closed before SASL negotiation finished.
>         at org.apache.hive.spark.client.rpc.Rpc$SaslClientHandler.dispose(Rpc.java:453)
>         at org.apache.hive.spark.client.rpc.SaslHandler.channelInactive(SaslHandler.java:90)
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)