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 11:22:12 GMT

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

Vinayakumar B commented on HDFS-8090:
-------------------------------------

bq. FSNamesystem#getECSchemas - do we need audit log here? Actually I got confused after going
through the existing logs, it looks like audit log has been done for getter calls also. For
example, getEZForPath, getfileinfo, listStatus et.
IMO audit log not required for this call as this is systemwide call. not particular to any
path. all the above calls referred are have a path.
Similar to this call is {{getStoragePolicies()}} which also doesnt have audit log.

> 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
(v6.3.4#6332)

Mime
View raw message