hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8090) Erasure Coding: Add RPC to client-namenode to list all ECSchemas loaded in Namenode.
Date Thu, 09 Apr 2015 16:11:12 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487589#comment-14487589

Vinayakumar B commented on HDFS-8090:

bq. In the latest patch chunkSize attribute is deleted from hdfs.proto, any specific reason
for this. But I could see if (this.options.containsKey(CHUNK_SIZE_KEY)) logic is still used
in ESSchema and got confused, am I missing anything?
Its because, While creating ECSchema, only way to set the chunksize is through options. If
its not present in options, default will be used. So while deserializing from protobuf, if
its present in options, it will be used. Otherwise default will be used. It need not be serialized
separately and added to options during deserialization.
Because of this, equals() was failing in test case, Since deserialized schema options had
the entry of the chunksize, where as default Schema was not having any options.

> Erasure Coding: Add RPC to client-namenode to list all ECSchemas loaded in Namenode.
> ------------------------------------------------------------------------------------
>                 Key: HDFS-8090
>                 URL: https://issues.apache.org/jira/browse/HDFS-8090
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-8090-01.patch, HDFS-8090-02.patch
> ECSchemas will be configured and loaded only at the Namenode to avoid conflicts.
> Client has to specify one of these schemas during creation of ecZones.
> So, add an RPC to ClientProtocol to get all ECSchemas loaded at namenode, so that client
can choose only any one of these.

This message was sent by Atlassian JIRA

View raw message