[
https://issues.apache.org/jira/browse/HDFS-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224412#comment-14224412
]
Vinayakumar B commented on HDFS-7210:
-------------------------------------
Failure is unrelated. Seems like it failed due to corrupted hadoop-common.jar
and failed to load core-default.xml
{noformat}2014-11-25 09:01:00,976 FATAL conf.Configuration
(Configuration.java:loadResource(2518)) - error parsing conf core-default.xml
java.util.zip.ZipException: invalid block type
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147)
at
java.util.zip.InflaterInputStream.read(InflaterInputStream.java:105){noformat}
> 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
>
>
> 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)
