Details
-
Bug
-
Status: Resolved
-
Trivial
-
Resolution: Fixed
-
3.0.0
-
None
-
3 Node SuSE Linux cluster
-
Reviewed
Description
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.
