hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9390) Block management for maintenance states
Date Sun, 16 Oct 2016 22:09:21 GMT

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

Hadoop QA commented on HDFS-9390:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} | {color:red}
HDFS-9390 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-9390 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12833649/HDFS-9390-2-branch-2.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/17176/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Block management for maintenance states
> ---------------------------------------
>
>                 Key: HDFS-9390
>                 URL: https://issues.apache.org/jira/browse/HDFS-9390
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: HDFS-9390-2-branch-2.patch, HDFS-9390-2.patch, HDFS-9390-3.patch,
HDFS-9390-4.patch, HDFS-9390-5.patch, HDFS-9390-branch-2.patch, HDFS-9390.patch
>
>
> When a node is transitioned to/stay in/transitioned out of maintenance state, we need
to make sure blocks w.r.t. that nodes are properly handled.
> * When nodes are put into maintenance, it will first go to ENTERING_MAINTENANCE, and
make sure blocks are minimally replicated before the nodes are transitioned to IN_MAINTENANCE.
> * Do not replica blocks when nodes are in maintenance states. Maintenance replica will
remain in BlockMaps and thus is still considered valid from block replication point of view.
In other words, putting a node to “maintenance” mode won’t trigger BlockManager to replicate
its blocks.
> * Do not invalidate replicas on node under maintenance. After any file's replication
factor is reduced, NN needs to invalidate some replicas. It should exclude nodes under maintenance
in the handling.
> * Do not put IN_MAINTENANCE replicas in LocatedBlock for read operation.
> * Do not allocate any new block on nodes under maintenance.
> * Have Balancer exclude nodes under maintenance.
> * Exclude nodes under maintenance for DN cache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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