[
https://issues.apache.org/jira/browse/HDFS-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B updated HDFS-11708:
---------------------------------
Attachment: HDFS-11708-07.patch
Trunk v07 patch seems to apply cleanly for me.
Re-attaching the same trunk patch again to verify by jenkins.
> Positional read will fail if replicas moved to different DNs after stream is
> opened
> -----------------------------------------------------------------------------------
>
> Key: HDFS-11708
> URL: https://issues.apache.org/jira/browse/HDFS-11708
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.7.3
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Priority: Critical
> Labels: release-blocker
> Attachments: HDFS-11708-01.patch, HDFS-11708-02.patch,
> HDFS-11708-03.patch, HDFS-11708-04.patch, HDFS-11708-05.patch,
> HDFS-11708-07.patch, HDFS-11708-07.patch, HDFS-11708-branch-2-07.patch,
> HDFS-11708-branch-2.7-07.patch, HDFS-11708-branch-2.8-07.patch,
> HDFS-11708-HDFS-11898-06.patch
>
>
> Scenario:
> 1. File was written to DN1, DN2 with RF=2
> 2. File stream opened to read and kept. Block Locations are [DN1,DN2]
> 3. One of the replica (DN2) moved to another datanode (DN3) due to datanode
> dead/balancing/etc.
> 4. Latest block locations in NameNode will be DN1 and DN3 in the 'same order'
> 5. DN1 went down, but not yet detected as dead in NameNode.
> 6. Client start reading using positional read api "read(pos, buf[], offset,
> length)"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
