[ https://issues.apache.org/jira/browse/HDFS-13897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621458#comment-16621458 ]
Anu Engineer commented on HDFS-13897: ------------------------------------- [~RANith] Thanks for the patch. I was wondering if we need the change in DiskBalancer.java. That change is already logged in the datanode logs. If we have a wrong value(an out of range value), I am worried this is going to fill up the datanode Logs. We seem to call {{getMaxError}} from line 909, which is a while loop, hence my concern. > DiskBalancer: for invalid configurations print WARN message in console output > while executing the Diskbalaner commands. > ----------------------------------------------------------------------------------------------------------------------- > > Key: HDFS-13897 > URL: https://issues.apache.org/jira/browse/HDFS-13897 > Project: Hadoop HDFS > Issue Type: Improvement > Components: diskbalancer > Reporter: Harshakiran Reddy > Assignee: Ranith Sardar > Priority: Minor > Attachments: HDFS-13897.patch > > > {{Scenario:-}} > 1. configure the invalid value for any disk balancer configurations and > restart the Datanode > 2. Run the disk balancer commands > {{Actual output:-}} > it's continue with default configurations > {{Excepted output:-}} > it will print WARN message in console like *configured invalid value and > taking the default value for this configuration* and that time user/customer > knows our configurations are not effected to current disk balancer otherwise > he will think it taking their configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org