hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16794) Default value for hive.spark.client.connect.timeout of 1000ms is too low
Date Sun, 11 Jun 2017 04:48:19 GMT

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

Eric Lin updated HIVE-16794:
----------------------------
    Status: Patch Available  (was: Open)

> Default value for hive.spark.client.connect.timeout of 1000ms is too low
> ------------------------------------------------------------------------
>
>                 Key: HIVE-16794
>                 URL: https://issues.apache.org/jira/browse/HIVE-16794
>             Project: Hive
>          Issue Type: Task
>          Components: Spark
>    Affects Versions: 2.1.1
>            Reporter: Eric Lin
>            Assignee: Eric Lin
>         Attachments: HIVE-16794.patch
>
>
> Currently the default timeout value for hive.spark.client.connect.timeout is set at 1000ms,
which is only 1 second. This is not enough when cluster is busy and user will constantly getting
the following timeout errors:
> {code}
> 17/05/03 03:20:08 ERROR yarn.ApplicationMaster: User class threw exception: java.util.concurrent.ExecutionException:
io.netty.channel.ConnectTimeoutException: connection timed out: <hs2-host>/172.19.22.11:35915

> java.util.concurrent.ExecutionException: io.netty.channel.ConnectTimeoutException: connection
timed out: <hs2-host>/172.19.22.11:35915 
> 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: io.netty.channel.ConnectTimeoutException: connection timed out: <hs2-host>/172.19.22.11:35915

> at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:220)

> at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) 
> at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120) 
> at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357)

> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) 
> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)

> at java.lang.Thread.run(Thread.java:745) 
> 17/05/03 03:20:08 INFO yarn.ApplicationMaster: Final app status: FAILED, exitCode: 15,
(reason: User class threw exception: java.util.concurrent.ExecutionException: io.netty.channel.ConnectTimeoutException:
connection timed out: <hs2-host>/172.19.22.11:35915) 
> 17/05/03 03:20:16 ERROR yarn.ApplicationMaster: SparkContext did not initialize after
waiting for 100000 ms. Please check earlier log output for errors. Failing the application.

> 17/05/03 03:20:16 INFO yarn.ApplicationMaster: Unregistering ApplicationMaster with FAILED
(diag message: User class threw exception: java.util.concurrent.ExecutionException: io.netty.channel.ConnectTimeoutException:
connection timed out: <hs2-host>/172.19.22.11:35915) 
> 17/05/03 03:20:16 INFO yarn.ApplicationMaster: Deleting staging directory .sparkStaging/application_1492040605432_11445

> 17/05/03 03:20:16 INFO util.ShutdownHookManager: Shutdown hook called
> {code}



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

Mime
View raw message