Skip to content

Conversation

@SaintBacchus
Copy link
Contributor

If the spark.blockMnager.port had conflicted with a specific port, Spark will throw an exception and exit.
So add a retry to avoid this situation.

@SaintBacchus SaintBacchus changed the title Add a retry to deal with the conflict port in netty server. [SPARK-5444][Network]Add a retry to deal with the conflict port in netty server. Jan 28, 2015
@SparkQA
Copy link

SparkQA commented Jan 28, 2015

Test build #26212 has finished for PR 4240 at commit cc926d2.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@andrewor14
Copy link
Contributor

LGTM merging this into master and 1.3. I added a few comments when I merged this.

asfgit pushed a commit that referenced this pull request Feb 6, 2015
…tty server.

If the `spark.blockMnager.port` had conflicted with a specific port, Spark will throw an exception and exit.
So add a retry to avoid this situation.

Author: huangzhaowei <[email protected]>

Closes #4240 from SaintBacchus/NettyPortConflict and squashes the following commits:

cc926d2 [huangzhaowei] Add a retry to deal with the conflict port in netty server.

(cherry picked from commit 2bda1c1)
Signed-off-by: Andrew Or <[email protected]>
@asfgit asfgit closed this in 2bda1c1 Feb 6, 2015
@SaintBacchus SaintBacchus deleted the NettyPortConflict branch December 26, 2015 06:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants