Return-Path: <hdfs-issues-return-164877-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 7E8DF200B5E
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 27 Jul 2016 07:48:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 7BD20160AA6; Wed, 27 Jul 2016 05:48:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id C09D3160AA4
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 27 Jul 2016 07:48:21 +0200 (CEST)
Received: (qmail 51122 invoked by uid 500); 27 Jul 2016 05:48:20 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 51090 invoked by uid 99); 27 Jul 2016 05:48:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jul 2016 05:48:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 973BC2C0D5F
	for <hdfs-issues@hadoop.apache.org>; Wed, 27 Jul 2016 05:48:20 +0000 (UTC)
Date: Wed, 27 Jul 2016 05:48:20 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12991907.1469209818000.142714.1469598500616@Atlassian.JIRA>
In-Reply-To: <JIRA.12991907.1469209818000@Atlassian.JIRA>
References: <JIRA.12991907.1469209818000@Atlassian.JIRA> <JIRA.12991907.1469209818830@arcas>
Subject: [jira] [Updated] (HDFS-10681) DiskBalancer: query command should
 report Plan file path apart from PlanID
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Wed, 27 Jul 2016 05:48:22 -0000


     [ https://issues.apache.org/jira/browse/HDFS-10681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Wang updated HDFS-10681:
-------------------------------
    Affects Version/s:     (was: HDFS-1312)
                       3.0.0-alpha1
     Target Version/s: 3.0.0-alpha1
        Fix Version/s:     (was: 3.0.0-alpha2)

> 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: 3.0.0-alpha1
>            Reporter: Manoj Govindassamy
>            Assignee: Manoj Govindassamy
>            Priority: Minor
>         Attachments: HDFS-10681-HDFS-1312.001.patch, HDFS-10681-HDFS-1312.002.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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org