hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11708) Positional read will fail if replicas moved to different DNs after stream is opened
Date Tue, 06 Jun 2017 05:43:18 GMT

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

Vinayakumar B commented on HDFS-11708:
--------------------------------------

Jenkins says v07 patch for trunk applies cleanly as well.
{noformat}============================================================================
============================================================================
                        Confirming git environment
============================================================================
============================================================================


HEAD is now at 66c6fd8 HADOOP-14431. ModifyTime of FileStatus returned by SFTPFileSystem's
getFileStatus method is wrong. Contributed by Hongyuan Li.
Previous HEAD position was 66c6fd8... HADOOP-14431. ModifyTime of FileStatus returned by SFTPFileSystem's
getFileStatus method is wrong. Contributed by Hongyuan Li.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 66c6fd831497944f4f49c5ce42c69a302b7d7bc0.
Already on 'trunk'
Your branch is up-to-date with 'origin/trunk'.
Current branch trunk is up to date.
Testing HDFS-11708 patch on trunk.


============================================================================
============================================================================
                          Re-execing under Docker
============================================================================
============================================================================{noformat}

> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message