[
https://issues.apache.org/jira/browse/SPARK-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083506#comment-15083506
]
Felix Cheung commented on SPARK-12609:
--------------------------------------
It looks like the timeout to socketConnection is merely the time from
establishment - we could hardcode it to something arbitrary long (eg. 1 day)
We should have some way to check if "is the JVM backend alive" - for that we
could have some kind of keep-alive ping for each request?
> Make R to JVM timeout configurable
> -----------------------------------
>
> Key: SPARK-12609
> URL: https://issues.apache.org/jira/browse/SPARK-12609
> Project: Spark
> Issue Type: Improvement
> Components: SparkR
> Reporter: Shivaram Venkataraman
>
> The timeout from R to the JVM is hardcoded at 6000 seconds in
> https://github.com/apache/spark/blob/6c5bbd628aaedb6efb44c15f816fea8fb600decc/R/pkg/R/client.R#L22
> This results in Spark jobs that take more than 100 minutes to always fail. We
> should make this timeout configurable through SparkConf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
