hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HDFS-4284) BlockReaderLocal not notified of failed disks
Date Tue, 28 Jan 2014 23:23:11 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jimmy Xiang reassigned HDFS-4284:
---------------------------------

    Assignee: Jimmy Xiang

> BlockReaderLocal not notified of failed disks
> ---------------------------------------------
>
>                 Key: HDFS-4284
>                 URL: https://issues.apache.org/jira/browse/HDFS-4284
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>    Affects Versions: 3.0.0, 2.0.2-alpha
>            Reporter: Andy Isaacson
>            Assignee: Jimmy Xiang
>
> When a DN marks a disk as bad, it stops using replicas on that disk.
> However a long-running {{BlockReaderLocal}} instance will continue to access replicas
on the failing disk.
> Somehow we should let the in-client BlockReaderLocal know that a disk has been marked
as bad so that it can stop reading from the bad disk.
> From HDFS-4239:
> bq. To rephrase that, a long running BlockReaderLocal will ride over local DN restarts
and disk "ejections". We had to drain the RS of all its regions in order to stop it from using
the bad disk.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message