[ https://issues.apache.org/jira/browse/SPARK-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Or closed SPARK-5691. ---------------------------- Resolution: Fixed Fix Version/s: 1.2.2 1.1.2 1.0.3 Assignee: Matthew Cheah Target Version/s: 1.0.3, 1.3.0, 1.1.2, 1.2.2 > Preventing duplicate registering of an application has incorrect logic > ---------------------------------------------------------------------- > > Key: SPARK-5691 > URL: https://issues.apache.org/jira/browse/SPARK-5691 > Project: Spark > Issue Type: Bug > Components: Deploy > Affects Versions: 1.1.1, 1.2.0 > Reporter: Matt Cheah > Assignee: Matthew Cheah > Fix For: 1.0.3, 1.3.0, 1.1.2, 1.2.2 > > > If an application registers twice with the Master, the Master accepts both > copies and they both show up in the UI and consume resources. This is > incorrect behavior. > This happens inadvertently in regular usage when the Master is under high > load, but it boils down to: when an application times out registering with > the master and sends a second registration message, but the Master is still > alive, it processes the first registration message for the application but > also erroneously processes the second registration message instead of > discarding it. -- 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