You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2017/05/11 00:43:04 UTC
[jira] [Commented] (YARN-6246) Identifying starved apps does not
need the scheduler writelock
[ https://issues.apache.org/jira/browse/YARN-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005727#comment-16005727 ]
Karthik Kambatla commented on YARN-6246:
----------------------------------------
Carefully looked through the locking. dumpStateInternal could race with the lastTimeAtMinShare value, but that shouldn't really be a problem.
While investigating this, I realized FSAppAttempt#updateDemand (called with the scheduler writelock) can be improved. Filed YARN-6582 for it.
> Identifying starved apps does not need the scheduler writelock
> --------------------------------------------------------------
>
> 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
> Attachments: YARN-6246.001.patch, YARN-6246.002.patch, YARN-6246.003.patch
>
>
> Currently, the starvation checks are done holding the scheduler writelock. We are probably better of doing this outside.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org