You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "LiXin Ge (JIRA)" <ji...@apache.org> on 2018/08/23 13:44:00 UTC
[jira] [Updated] (HDDS-336) Print out container location
information for a specific ozone key
[ https://issues.apache.org/jira/browse/HDDS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
LiXin Ge updated HDDS-336:
--------------------------
Attachment: HDDS-336.000.patch
> Print out container location information for a specific ozone key
> ------------------------------------------------------------------
>
> Key: HDDS-336
> URL: https://issues.apache.org/jira/browse/HDDS-336
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: SCM
> Reporter: Elek, Marton
> Assignee: LiXin Ge
> Priority: Major
> Labels: newbie
> Fix For: 0.2.1
>
> Attachments: HDDS-336.000.patch
>
>
> In the protobuf protocol we have all the containerid/localid(=blockid) information for a specific ozone key.
> It would be a big help to print out this information to the command line with the ozone cli.
> It requires to improve the REST and RPC interface with additionalOzone KeyLocation information.
> It would help a very big help during the test of the current scm behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org