hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-6246) Move app starvation identification out of the update thread
Date Mon, 27 Feb 2017 22:26:45 GMT
Karthik Kambatla created YARN-6246:

             Summary: Move app starvation identification out of the update thread
                 Key: YARN-6246
                 URL: https://issues.apache.org/jira/browse/YARN-6246
             Project: Hadoop YARN
          Issue Type: Sub-task
          Components: fairscheduler
    Affects Versions: 2.9.0
            Reporter: Karthik Kambatla
            Assignee: Karthik Kambatla

Given the update thread holds the scheduler write-lock, we are probably better of computing
starvation and identification of starved apps in a different thread. 

I am averse to adding a thread that runs on a *configurable timeout*, but maybe we could trigger
this thread after every update run, or do this in the update thread but outside of the write-lock.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message