Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 22 Feb 2017 19:10:44 +0000 (UTC)
From: "Ravi Prakash (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13044707.1487650951000.34223.1487790644089@Atlassian.JIRA>
In-Reply-To: <JIRA.13044707.1487650951000@Atlassian.JIRA>
References: <JIRA.13044707.1487650951000@Atlassian.JIRA> <JIRA.13044707.1487650951460@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-11435) NameNode should track open for
 write files lengths more frequent than on newer block allocations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Feb 2017 19:10:48 -0000


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

Ravi Prakash commented on HDFS-11435:
-------------------------------------

Thanks Manoj! I'll continue the discussion on HDFS-11402. Thanks for volunteering to fix that btw. Its really important

> NameNode should track open for write files lengths more frequent than on newer block allocations
> ------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-11435
>                 URL: https://issues.apache.org/jira/browse/HDFS-11435
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Manoj Govindassamy
>            Assignee: Manoj Govindassamy
>
> *Problem:*
> Currently the length of an open for write / Under construction file is updated on the NameNode only when 
> # Block boundary: On block boundaries and upon allocation of new Block, NameNode gets to know the file growth and the file length catches up
> # hsync(SyncFlag.UPDATE_LENGTH): Upon Client apps invoking a hsync on the write stream with a special flag, DataNodes send an incremental block report with the latest file length which NameNode uses it to update its meta data.
> # First hflush() on the new Block: Upon Client apps doing first time hflush() on an every new Block, DataNodes notifies NameNode about the latest file length.
> # Output stream close: Forces DataNodes update NameNode about the file length after data persistence and proper acknowledgements in the pipeline.
> So, lengths for open for write files are usually a lot less than the length seen by the DN/client. Highly preferred to have NameNode not lagging in file lengths by order of Block size for under construction files and to have more frequent, scalable update mechanism for these open file lengths. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org