[
https://issues.apache.org/jira/browse/HDFS-12948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee updated HDFS-12948:
---------------------------------------
Attachment: HDFS-12948.001.patch
Patch v1 handles the case where if the top limit specified for report command
is not valid, it throws an exception.
[~anu], please have a look.
> DiskBalancer report command top option should only take positive numeric
> values
> -------------------------------------------------------------------------------
>
> Key: HDFS-12948
> URL: https://issues.apache.org/jira/browse/HDFS-12948
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Minor
> Attachments: HDFS-12948.001.patch
>
>
> Currently , diskBalancer report command "top" option takes values like "AAA"
> as well negative/decimal values and gives output. These invalid values should
> not be processed and some error/warning should be given.
> For Example,
> $ hdfs diskbalancer -report -top -100
> 17/12/19 15:07:01 INFO command.Command: Processing report command
> 17/12/19 15:07:02 INFO balancer.KeyManager: Block token params received from
> NN: update interval=10hrs, 0sec, token lifetime=10hrs, 0sec
> 17/12/19 15:07:02 INFO block.BlockTokenSecretManager: Setting block keys
> 17/12/19 15:07:02 INFO balancer.KeyManager: Update block keys every 2hrs,
> 30mins, 0sec
> 17/12/19 15:07:02 INFO command.Command: Reporting top -100 DataNode(s)
> benefiting from running DiskBalancer.
> Processing report command
> Reporting top -100 DataNode(s) benefiting from running DiskBalancer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
