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 "Fei Hui (Jira)" <ji...@apache.org> on 2019/08/29 07:41:00 UTC
[jira] [Updated] (HDFS-14796) Define LOG instead of
BlockManager.LOG in ErasureCodingWork
[ https://issues.apache.org/jira/browse/HDFS-14796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fei Hui updated HDFS-14796:
---------------------------
Summary: Define LOG instead of BlockManager.LOG in ErasureCodingWork (was: Define LOG instead of in ErasureCodingWork)
> Define LOG instead of BlockManager.LOG in ErasureCodingWork
> -----------------------------------------------------------
>
> 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
> Priority: Major
>
> 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