You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2017/10/17 11:25:00 UTC

[jira] [Commented] (SPARK-22294) Reset spark.driver.bindAddress when starting a Checkpoint

    [ https://issues.apache.org/jira/browse/SPARK-22294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207509#comment-16207509 ] 

Apache Spark commented on SPARK-22294:
--------------------------------------

User 'ssaavedra' has created a pull request for this issue:
https://github.com/apache/spark/pull/19427

> Reset spark.driver.bindAddress when starting a Checkpoint
> ---------------------------------------------------------
>
>                 Key: SPARK-22294
>                 URL: https://issues.apache.org/jira/browse/SPARK-22294
>             Project: Spark
>          Issue Type: Improvement
>          Components: Deploy, Spark Core
>    Affects Versions: 2.1.0, 2.2.0
>            Reporter: Santiago Saavedra
>              Labels: newbie
>
> On SPARK-4563 support for binding the driver to a different address than the spark.driver.host was provided so that the driver could be running under a differently-routed network. However, when the driver fails, the Checkpoint restoring function expects that the {{spark.driver.bindAddress}} remains the same even if the {{spark.driver.host}} variable may change. That limits the capabilities of recovery under several cluster configurations, and we propose that {{spark.driver.bindAddress}} should have the same replacement behaviour as {{spark.driver.host}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org