[
https://issues.apache.org/jira/browse/HDFS-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717836#comment-14717836
]
Vinod Kumar Vavilapalli edited comment on HDFS-7213 at 8/30/15 6:50 PM:
------------------------------------------------------------------------
This wasn't originally in 2.6.1, must have been committed to 2.6, which was
already 2.6.2. I just committed this to 2.6.1 taking [~sjlee0]'s cherry-pick,
which must have come from branch-2.6.
Ran compilation before the push.
was (Author: vinodkv):
This wasn't originally in 2.6.1, must have been committed to 2.6, which was
already 2.6.2. I just committed this to 2.6.1 taking [~sjlee0]'s cherry-pick,
which must have come from branch-2.6.
Ran compilation and TestDFSClientRetries before the push.
> 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, 2.6.1
>
> 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)
