GitHub user tdas opened a pull request:

    https://github.com/apache/spark/pull/5024

    [SPARK-6331] Load new master URL if present when recovering streaming 
context from checkpoint

    In streaming driver recovery, when the SparkConf is reconstructed based on 
the checkpointed configuration, it recovers the old master URL. This okay if 
the cluster on which the streaming application is relaunched is the same 
cluster as it was running before. But if that cluster changes, there is no way 
to inject the new master URL of the new cluster. As a result, the restarted app 
tries to connect to the non-existent old cluster and fails. 
    
    The solution is to check whether a master URL is set in the System 
properties (by Spark submit) before recreating the SparkConf. If a new master 
url is set in the properties, then use it as that is obviously the most 
relevant one. Otherwise load the old one (to maintain existing behavior). 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tdas/spark SPARK-6331

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/5024.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5024
    
----
commit 222485d3f93143ff46cc8473ab6f1b1a3a23ecb0
Author: Tathagata Das <[email protected]>
Date:   2015-03-14T01:58:15Z

    Load new master URL if present when recovering streaming context from 
checkpoint

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to