You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Ming Ma (JIRA)" <ji...@apache.org> on 2015/07/29 23:23:05 UTC

[jira] [Commented] (HDFS-7213) processIncrementalBlockReport performance degradation

    [ https://issues.apache.org/jira/browse/HDFS-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646784#comment-14646784 ] 

Ming Ma commented on HDFS-7213:
-------------------------------

For the 2.6.1 effort, this jira can be cleanly backported to branch-2.6.

> processIncrementalBlockReport performance degradation
> -----------------------------------------------------
>
>                 Key: HDFS-7213
>                 URL: https://issues.apache.org/jira/browse/HDFS-7213
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.4.0
>            Reporter: Daryn Sharp
>            Assignee: Eric Payne
>            Priority: Critical
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0
>
>         Attachments: HDFS-7213.1412804753, HDFS-7213.1412806496.txt
>
>
> {{BlockManager#processIncrementalBlockReport}} has a debug line that is missing a {{isDebugEnabled}} check.  The write lock is being held.  Coupled with the increase in incremental block reports from receiving blocks, under heavy load this log line noticeably degrades performance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)