You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Surendra Singh Lilhore (Jira)" <ji...@apache.org> on 2019/10/12 07:12:00 UTC
[jira] [Commented] (HDFS-14384) When lastLocatedBlock token expire,
it will take 1~3s second to refetch it.
[ https://issues.apache.org/jira/browse/HDFS-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949940#comment-16949940 ]
Surendra Singh Lilhore commented on HDFS-14384:
-----------------------------------------------
Attached v2 patch, assigned newBlocks directly to locatedBlocks.
> When lastLocatedBlock token expire, it will take 1~3s second to refetch it.
> ---------------------------------------------------------------------------
>
> Key: HDFS-14384
> URL: https://issues.apache.org/jira/browse/HDFS-14384
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.7.2
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Priority: Major
> Attachments: HDFS-14384.001.patch, HDFS-14384.002.patch
>
>
> Scenario :
> 1. Write file with one block which is in-progress.
> 2. Open input stream and close the output stream.
> 3. Wait for block token expiration and read the data.
> 4. Last block read take 1~3 sec to read it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org