[
https://issues.apache.org/jira/browse/HDFS-10681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390548#comment-15390548
]
Manoj Govindassamy commented on HDFS-10681:
-------------------------------------------
Docker build failure has below signature. Looks like an infra issue.
{noformat}
---> Using cache
---> cf7a3f0511cb
Step 6 : RUN curl -s -S -L
http://http.us.debian.org/debian/pool/main/libi/libisal/libisal2_2.15.0-2_amd64.deb
-o /opt/libisal2_2.15.0-2_amd64.deb && dpkg -i
/opt/libisal2_2.15.0-2_amd64.deb
---> Running in 86e44578fb9f
[91mdpkg-deb: error: `/opt/libisal2_2.15.0-2_amd64.deb' is not a debian format
archive
dpkg: error processing archive /opt/libisal2_2.15.0-2_amd64.deb (--install):
subprocess dpkg-deb --control returned error exit status 2
[0m[91mErrors were encountered while processing:
/opt/libisal2_2.15.0-2_amd64.deb
[0mThe command '/bin/sh -c curl -s -S -L
http://http.us.debian.org/debian/pool/main/libi/libisal/libisal2_2.15.0-2_amd64.deb
-o /opt/libisal2_2.15.0-2_amd64.deb && dpkg -i
/opt/libisal2_2.15.0-2_amd64.deb' returned a non-zero code: 1
{noformat}
> DiskBalancer: query command should report Plan file path apart from PlanID
> --------------------------------------------------------------------------
>
> Key: HDFS-10681
> URL: https://issues.apache.org/jira/browse/HDFS-10681
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: diskbalancer
> Affects Versions: HDFS-1312
> Reporter: Manoj Govindassamy
> Assignee: Manoj Govindassamy
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: HDFS-10681-HDFS-1312.001.patch
>
>
> DiskBalancer query command currently reports planID (SHA512 hex) only.
> Currently ongoing disk balancing activity in a datanode can be cancelled
> wither by planID + datanode_address or just by pointing to the right plan
> file. Since there could be many plan files, to avoid ambiguity its better if
> query command can report the plan file path also.
> {noformat}
> $ hdfs diskbalancer --help query
> usage: hdfs diskbalancer -query <hostname> [options]
> Query Plan queries a given data node about the current state of disk
> balancer execution.
> --query <arg> Queries the disk balancer status of a given datanode.
> Query command retrievs *the plan ID* and the current running state.
> {noformat}
> Sample query command output:
> {noformat}
> 16/06/20 15:42:16 INFO command.Command: Executing "query plan" command.
> Plan ID:
> 04f41e2e1fa2d63558284be85155ea68154fb6ab435f1078c642d605d06626f176da16b321b35c99f1f6cd0cd77090c8743bb9a19190c4a01b5f8c51a515e240
> Result: PLAN_UNDER_PROGRESS
> or
> 16/06/20 15:46:09 INFO command.Command: Executing "query plan" command.
> Plan ID:
> 04f41e2e1fa2d63558284be85155ea68154fb6ab435f1078c642d605d06626f176da16b321b35c99f1f6cd0cd77090c8743bb9a19190c4a01b5f8c51a515e240
> Result: PLAN_DONE
> {noformat}
> Cancel command syntax:
> {noformat}
> $ hdfs diskbalancer --help cancel
> *usage: hdfs diskbalancer -cancel <planFile> | -cancel <planID> -node
> <hostname>*
> Cancel command cancels a running disk balancer operation.
> --cancel <arg> Cancels a running plan using a plan file.
> --node <arg> Cancels a running plan using a plan ID and hostName
> Cancel command can be run via pointing to a plan file, or by reading the
> plan ID using the query command and then using planID and hostname.
> Examples of how to run this command are
> hdfs diskbalancer -cancel <planfile>
> hdfs diskbalancer -cancel <planID> -node <hostname>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
