GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/309

    [FLINK-1376] [runtime] Add proper shared slot release in case of a fatal 
TaskManager failure

    This PR introduces SharedSlots as being a special Slot type and as such 
being released properly in case an Instance has been marked dead. This fixes 
the problem that a dead instance, which has not been shutdown properly, causes 
a job not being removed properly from the system, because it is not aware of 
the SubSlots.
    
    Adds test cases where only the task manager is killed by a Kill message 
(hard shutdown)
    
    @StephanEwen: Requires thorough review because it touches some delicate 
scheduling/slot logic.

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

    $ git pull https://github.com/tillrohrmann/flink fixSharedSlotReleaseAkka

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

    https://github.com/apache/flink/pull/309.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 #309
    
----
commit ba1dd8b2ce956eb1b14a0ca458a3ca5240da0aee
Author: Till Rohrmann <[email protected]>
Date:   2015-01-12T09:58:45Z

    [FLINK-1376] [runtime] Add proper shared slot release in case of a fatal 
TaskManager failure.
    
    Fixes concurrent modification exception of SharedSlot's subSlots field by 
synchronizing all state changing operations through the associated assignment 
group. Fixes deadlock where Instance.markDead first acquires InstanceLock and 
then by releasing the associated slots the assignment group lockcan block with 
a direct releaseSlot call on a SharedSlot which first acquires the assignment 
group lock and then the instance lock in order to return the slot to the 
instance.

----


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

Reply via email to