{"push_id":604372590,"size":1,"distinct_size":1,"ref":"refs/heads/branch-1.3","head":"95f8d1c51dabf89a50985d488ac68977ebaf9771","before":"426816b5ca42443b99e8af7a6450604dd7794bd6","commits":[{"sha":"95f8d1c51dabf89a50985d488ac68977ebaf9771","author":{"email":"4330a85689689e23b81e88bdf5853b25c33529eb@gmail.com","name":"Tathagata Das"},"message":"[SPARK-6331] Load new master URL if present when recovering streaming context from checkpoint\n\nIn 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.\n\nThe 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).\n\nAuthor: Tathagata Das <tathagata.das1565@gmail.com>\n\nCloses #5024 from tdas/SPARK-6331 and squashes the following commits:\n\n392fd44 [Tathagata Das] Fixed naming issue.\nc7c0b99 [Tathagata Das] Addressed comments.\n6a0857c [Tathagata Das] Updated testsuites.\n222485d [Tathagata Das] Load new master URL if present when recovering streaming context from checkpoint\n\n(cherry picked from commit c928796ade54f68e26bc55734a9867a046d2e3fe)\nSigned-off-by: Tathagata Das <tathagata.das1565@gmail.com>","distinct":true,"url":"https://api.github.com/repos/apache/spark/commits/95f8d1c51dabf89a50985d488ac68977ebaf9771"}]}