hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7210) Avoid two separate RPC's namenode.append() and namenode.getFileInfo() for an append call from DFSClient
Date Fri, 28 Nov 2014 08:53:12 GMT

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

Uma Maheswara Rao G commented on HDFS-7210:
-------------------------------------------

+1 on the changes.Vinay, If  you +1 on the delta changes I made, I will proceed for committing
it.

> Avoid two separate RPC's namenode.append() and namenode.getFileInfo() for an append call
from DFSClient
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7210
>                 URL: https://issues.apache.org/jira/browse/HDFS-7210
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client, namenode
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-7210-001.patch, HDFS-7210-002.patch, HDFS-7210-003.patch, HDFS-7210-004.patch,
HDFS-7210-005.patch, HDFS-7210-006.patch
>
>
> Currently DFSClient does 2 RPCs to namenode for an append operation.
> {{append()}} for re-opening the file and getting the last block, 
> {{getFileInfo()}} Another on to get HdfsFileState
> If we can combine result of these 2 calls and make one RPC, then it can reduce load on
NameNode.
> For the backward compatibility we need to keep existing {{append()}} call as is



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message