[
https://issues.apache.org/jira/browse/YARN-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-6246:
-----------------------------------
Attachment: YARN-6246.005.patch
Looked at it again with fresh eyes and the long-term safer approach seemed to
call dumpSchedulerState holding the scheduler readlock.
This aligns well with our general thinking around coarse-grained read/write
locks in the scheduler.
[~templedf] - what do you think?
> 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, YARN-6246.004.patch, YARN-6246.005.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: [email protected]
For additional commands, e-mail: [email protected]
