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/02/07 22:27:41 UTC
[jira] [Commented] (YARN-6112)
fsOpDurations.addUpdateCallDuration() should be independent to LOG level
[ https://issues.apache.org/jira/browse/YARN-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856930#comment-15856930 ]
Karthik Kambatla commented on YARN-6112:
----------------------------------------
+1 on the trunk patch. [~yufeigu] - can you post another patch for branch-2 that keeps the metric, but fixes the original problem reported on this JIRA?
> fsOpDurations.addUpdateCallDuration() should be independent to LOG level
> ------------------------------------------------------------------------
>
> Key: YARN-6112
> URL: https://issues.apache.org/jira/browse/YARN-6112
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Reporter: Yufei Gu
> Assignee: Yufei Gu
> Attachments: YARN-6112.001.patch, YARN-6112.002.patch, YARN-6112.003.patch
>
>
> In the update thread of Fair Scheduler, the {{fsOpDurations.addUpdateCallDuration()}} records the duration of {{update()}}, it should be independent to LOG level. YARN-4752 put the it inside a {{LOG.isDebugEnabled()}} block. Not sure any particular reason to do that. cc [~kasha]
--
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