hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4350) Make enabling of stale marking on read and write paths independent
Date Wed, 23 Jan 2013 18:53:14 GMT

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

Suresh Srinivas commented on HDFS-4350:
---------------------------------------

One additional comment - if the config name is changed, it should go into both branch-1 and
branch-2. That way the migration from 1.x release to 2.x is not complicated due to the need
to change config name.
                
> Make enabling of stale marking on read and write paths independent
> ------------------------------------------------------------------
>
>                 Key: HDFS-4350
>                 URL: https://issues.apache.org/jira/browse/HDFS-4350
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: hdfs-4350-1.patch, hdfs-4350-2.patch, hdfs-4350-3.patch, hdfs-4350-4.patch,
hdfs-4350-5.patch, hdfs-4350.txt
>
>
> Marking of datanodes as stale for the read and write path was introduced in HDFS-3703
and HDFS-3912 respectively. This is enabled using two new keys, {{DFS_NAMENODE_CHECK_STALE_DATANODE_KEY}}
and {{DFS_NAMENODE_AVOID_STALE_DATANODE_FOR_WRITE_KEY}}. However, there currently exists a
dependency, since you cannot enable write marking without also enabling read marking, since
the first key enables both checking of staleness and read marking.
> I propose renaming the first key to {{DFS_NAMENODE_AVOID_STALE_DATANODE_FOR_READ_KEY}},
and make checking enabled if either of the keys are set. This will allow read and write marking
to be enabled independently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message