hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "LiXin Ge (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-336) Print out container location information for a specific ozone key
Date Thu, 16 Aug 2018 08:59:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582228#comment-16582228
] 

LiXin Ge commented on HDDS-336:
-------------------------------

Thanks [~elek] for theĀ fineĀ details. I have assigned it to myself and will work on it soon.

> 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
>
>
> 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


Mime
View raw message