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 "Ayush Saxena (JIRA)" <ji...@apache.org> on 2018/08/07 14:37:00 UTC
[jira] [Assigned] (HDFS-13772) Erasure coding: Unnecessary NameNode
Logs displaying for Enabling/Disabling Erasure coding policies which are
already enabled/disabled
[ https://issues.apache.org/jira/browse/HDFS-13772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ayush Saxena reassigned HDFS-13772:
-----------------------------------
Assignee: Ayush Saxena
> Erasure coding: Unnecessary NameNode Logs displaying for Enabling/Disabling Erasure coding policies which are already enabled/disabled
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-13772
> URL: https://issues.apache.org/jira/browse/HDFS-13772
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: erasure-coding
> Affects Versions: 3.0.0
> Environment: 3 Node SuSE Linux cluster
> Reporter: Souryakanta Dwivedy
> Assignee: Ayush Saxena
> Priority: Trivial
> Attachments: EC_capture1.PNG
>
>
> Unnecessary NameNode Logs displaying for Enabling/Disabling Erasure coding policies which are already enabled/disabled
> - Enable any Erasure coding policy like "RS-LEGACY-6-3-1024k"
> - Check the console log display as "Erasure coding policy RS-LEGACY-6-3-1024k is enabled"
> - Again try to enable the same policy multiple times "hdfs ec -enablePolicy -policy RS-LEGACY-6-3-1024k"
> instead of throwing error message as ""policy already enabled"" it will display same messages as "Erasure coding policy RS-LEGACY-6-3-1024k is enabled"
> - Also in NameNode log policy enabled logs are displaying multiple times unnecessarily even though the policy is already enabled.
> like this : 2018-07-27 18:50:35,084 INFO org.apache.hadoop.hdfs.server.namenode.ErasureCodingPolicyManager: Disable the erasure coding policy RS-10-4-1024k
> 2018-07-27 18:50:35,084 INFO org.apache.hadoop.hdfs.server.namenode.ErasureCodingPolicyManager: Disable the erasure coding policy RS-10-4-1024k
> 2018-07-27 18:50:35,084 INFO org.apache.hadoop.hdfs.server.namenode.ErasureCodingPolicyManager: Disable the erasure coding policy RS-10-4-1024k
> 2018-07-27 18:50:35,084 INFO org.apache.hadoop.hdfs.server.namenode.ErasureCodingPolicyManager: Enable the erasure coding policy RS-LEGACY-6-3-1024k
> 2018-07-27 18:50:35,084 INFO org.apache.hadoop.hdfs.server.namenode.ErasureCodingPolicyManager: Enable the erasure coding policy RS-LEGACY-6-3-1024k
> 2018-07-27 18:50:35,084 INFO org.apache.hadoop.hdfs.server.namenode.ErasureCodingPolicyManager: Enable the erasure coding policy RS-LEGACY-6-3-1024k
> - While executing the Erasure coding policy disable command also same type of logs coming multiple times even though the policy is already
> disabled.It should throw error message as ""policy is already disabled"" for already disabled policy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org