hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5946) Webhdfs DN choosing code is flawed
Date Sun, 05 Jun 2016 05:59:59 GMT

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

Vinod Kumar Vavilapalli updated HDFS-5946:
    Target Version/s:   (was: 2.8.0)

Not much going on here for a long time, dropping from 2.8.0.

Not putting any target-version either anymore, let's target this depending on when there is
patch activity.

> Webhdfs DN choosing code is flawed
> ----------------------------------
>                 Key: HDFS-5946
>                 URL: https://issues.apache.org/jira/browse/HDFS-5946
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode, webhdfs
>    Affects Versions: 2.4.0, 3.0.0-alpha1
>            Reporter: Daryn Sharp
>            Priority: Critical
> HDFS-5891 improved the performance of redirecting webhdfs clients to a DN.  Instead of
attempting a connection with a 1-minute timeout, the NN skips decommissioned nodes.
> The logic appears flawed.  It finds the index of the first decommissioned node, if any,
> * Throws an exception if index = 0, even if other nodes later in the list are not decommissioned.
> * Else picks a random node prior to the index.  Let's say there are 10 replicas, 2nd
location is decommissioned.  All clients will be redirected to the first location even though
there are 8 other valid locations.

This message was sent by Atlassian JIRA

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

View raw message