[
https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du updated YARN-3304:
-----------------------------
Attachment: YARN-3304-v8.patch
There are still two issues with v7 version:
1. cpuTimeMs in WindowsBasedProcessTree as a global variable is updated to
local variable in previous patches which is unexpected.
2. In Task.java, a potential bug (existing before this patch) if cpuTime is
UNAVAILABLE, but initCpuCumulativeTime is AVAILABLE, then we could put negative
value to resource counter.
Fix both in v8 patch.
> ResourceCalculatorProcessTree#getCpuUsagePercent default return value is
> inconsistent with other getters
> --------------------------------------------------------------------------------------------------------
>
> Key: YARN-3304
> URL: https://issues.apache.org/jira/browse/YARN-3304
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Junping Du
> Assignee: Junping Du
> Priority: Blocker
> Attachments: YARN-3304-v2.patch, YARN-3304-v3.patch,
> YARN-3304-v4-boolean-way.patch, YARN-3304-v4-negative-way-MR.patch,
> YARN-3304-v4-negtive-value-way.patch, YARN-3304-v6-no-rename.patch,
> YARN-3304-v6-with-rename.patch, YARN-3304-v7.patch, YARN-3304-v8.patch,
> YARN-3304.patch, yarn-3304-5.patch
>
>
> Per discussions in YARN-3296, getCpuUsagePercent() will return -1 for
> unavailable case while other resource metrics are return 0 in the same case
> which sounds inconsistent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
