[
https://issues.apache.org/jira/browse/HDDS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594917#comment-16594917
]
LiXin Ge commented on HDDS-336:
-------------------------------
Thanks [~elek] for the detailed comments and information.
{quote}
Because ContainerId is not unique the Map<Long,Long> is not good enough to
store the location information. (one container could have (c1,l1), (c1,l2)
blocks an in that case the map would do a c1->l2 from this information)
{quote}
List<Map<Long,Long>> can handles this situation, in that case there will have
two Map entries in the List with the same container ID.
But creating a specific class sounds better, I didn't do that in patch 002 just
bacause afraid to create too many classes: one for OzoneLocation, one for RPC
location response, one for REST location response, etc. This is done in patch
003 besides the Cli print improvment now.
Thanks again for your help.
> 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, HDDS-336.001.patch,
> HDDS-336.002.patch, HDDS-336.003.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: [email protected]
For additional commands, e-mail: [email protected]
