spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Cheah (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SPARK-5691) Preventing duplicate registering of an application has incorrect logic
Date Mon, 09 Feb 2015 18:55:35 GMT
Matt Cheah created SPARK-5691:
---------------------------------

             Summary: 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
    Affects Versions: 1.2.0, 1.1.1
            Reporter: Matt Cheah
             Fix For: 1.3.0


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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message