You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2016/01/20 18:46:39 UTC
[jira] [Commented] (UIMA-4742) DUCC RM: Never deallocate
non-preemptable shares
[ https://issues.apache.org/jira/browse/UIMA-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109022#comment-15109022 ]
Jim Challenger commented on UIMA-4742:
--------------------------------------
Update to the policy:
For vary-off: leave all work in place EXCEPT for fair-share jobs, whose processes will be purged.
For node death: purge all work EXCEPT reservations
Note 5 classes of work to consider.
1. reservation, 2. arbitrary process, 3. fair-share job, 4. service instance, 5. Job submitted to a non-preemptable class.
> DUCC RM: Never deallocate non-preemptable shares
> -------------------------------------------------
>
> Key: UIMA-4742
> URL: https://issues.apache.org/jira/browse/UIMA-4742
> Project: UIMA
> Issue Type: Task
> Components: DUCC
> Affects Versions: 2.0.1-Ducc
> Reporter: Jim Challenger
> Assignee: Jim Challenger
> Fix For: 2.1.0-Ducc
>
>
> Design change - never deallocate non-preemptable shares until the job is completed in some way. The shares stay allocated under all these conditions, some of which may require manual attention to clear the job:
> - vary off
> - node failure
> - misconfiguration
> Previously, jobs in class FIXED, services, and APs would be purged because they can be started elsewhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)