GitHub user alexrovner opened a pull request:

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

     [SPARK-5529][CORE]Add expireDeadHosts in HeartbeatReceiver

    If a blockManager has not send heartBeat more than 120s, 
BlockManagerMasterActor will remove it. But coarseGrainedSchedulerBackend can 
only remove executor after an DisassociatedEvent.  We should expireDeadHosts at 
HeartbeatReceiver.
    
    Author: Hong Shen <[email protected]>
    
    Closes #4363 from shenh062326/my_change3 and squashes the following commits:
    
    2c9a46a [Hong Shen] Change some code style.
    1a042ff [Hong Shen] Change some code style.
    2dc456e [Hong Shen] Change some code style.
    d221493 [Hong Shen] Fix test failed
    7448ac6 [Hong Shen] A minor change in sparkContext and heartbeatReceiver
    b904aed [Hong Shen] Fix failed test
    52725af [Hong Shen] Remove assert in SparkContext.killExecutors
    5bedcb8 [Hong Shen] Remove assert in SparkContext.killExecutors
    a858fb5 [Hong Shen] A minor change in HeartbeatReceiver
    3e221d9 [Hong Shen] A minor change in HeartbeatReceiver
    6bab7aa [Hong Shen] Change a code style.
    07952f3 [Hong Shen] Change configs name and code style.
    ce9257e [Hong Shen] Fix test failed
    bccd515 [Hong Shen] Fix test failed
    8e77408 [Hong Shen] Fix test failed
    c1dfda1 [Hong Shen] Fix test failed
    e197e20 [Hong Shen] Fix test failed
    fb5df97 [Hong Shen] Remove ExpireDeadHosts in BlockManagerMessages
    b5c0441 [Hong Shen] Remove expireDeadHosts in BlockManagerMasterActor
    c922cb0 [Hong Shen] Add expireDeadHosts in HeartbeatReceiver

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

    $ git pull https://github.com/alexrovner/spark SPARK-5529-backport-1.3-v2

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

    https://github.com/apache/spark/pull/5793.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 #5793
    
----
commit f238f94fa2081ac861533172ba089303c5b4d0bf
Author: Hong Shen <[email protected]>
Date:   2015-02-27T02:43:23Z

     [SPARK-5529][CORE]Add expireDeadHosts in HeartbeatReceiver
    
    If a blockManager has not send heartBeat more than 120s, 
BlockManagerMasterActor will remove it. But coarseGrainedSchedulerBackend can 
only remove executor after an DisassociatedEvent.  We should expireDeadHosts at 
HeartbeatReceiver.
    
    Author: Hong Shen <[email protected]>
    
    Closes #4363 from shenh062326/my_change3 and squashes the following commits:
    
    2c9a46a [Hong Shen] Change some code style.
    1a042ff [Hong Shen] Change some code style.
    2dc456e [Hong Shen] Change some code style.
    d221493 [Hong Shen] Fix test failed
    7448ac6 [Hong Shen] A minor change in sparkContext and heartbeatReceiver
    b904aed [Hong Shen] Fix failed test
    52725af [Hong Shen] Remove assert in SparkContext.killExecutors
    5bedcb8 [Hong Shen] Remove assert in SparkContext.killExecutors
    a858fb5 [Hong Shen] A minor change in HeartbeatReceiver
    3e221d9 [Hong Shen] A minor change in HeartbeatReceiver
    6bab7aa [Hong Shen] Change a code style.
    07952f3 [Hong Shen] Change configs name and code style.
    ce9257e [Hong Shen] Fix test failed
    bccd515 [Hong Shen] Fix test failed
    8e77408 [Hong Shen] Fix test failed
    c1dfda1 [Hong Shen] Fix test failed
    e197e20 [Hong Shen] Fix test failed
    fb5df97 [Hong Shen] Remove ExpireDeadHosts in BlockManagerMessages
    b5c0441 [Hong Shen] Remove expireDeadHosts in BlockManagerMasterActor
    c922cb0 [Hong Shen] Add expireDeadHosts in HeartbeatReceiver

----


---
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