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 "Surendra Singh Lilhore (Jira)" <ji...@apache.org> on 2019/08/30 09:05:00 UTC
[jira] [Commented] (HDFS-14796) Define LOG instead of
BlockManager.LOG in ErasureCodingWork/ReplicationWork
[ https://issues.apache.org/jira/browse/HDFS-14796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919345#comment-16919345 ]
Surendra Singh Lilhore commented on HDFS-14796:
-----------------------------------------------
Thanks [~ferhui] for contribution
committed ti trunk.
> Define LOG instead of BlockManager.LOG in ErasureCodingWork/ReplicationWork
> ---------------------------------------------------------------------------
>
> Key: HDFS-14796
> URL: https://issues.apache.org/jira/browse/HDFS-14796
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.4, 3.3.0, 3.2.1, 3.1.3
> Reporter: Fei Hui
> Assignee: Fei Hui
> Priority: Major
> Attachments: HDFS-14796.001.patch, HDFS-14796.002.patch, HDFS-14796.003.patch
>
>
> There are too many noisy logs with BlockManager.LOG, it's too hard to debug problem. Define LOG instead of it in ErasureCodingWork.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org