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

Hadoop QA commented on HDFS-12066:
----------------------------------

| (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  5s{color} 
| {color:red} HDFS-12066 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-12066 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12881125/HDFS-12054.002.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/20627/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> When Namenode is in safemode,may not allowed to remove an user's erasure 
> coding policy
> --------------------------------------------------------------------------------------
>
>                 Key: HDFS-12066
>                 URL: https://issues.apache.org/jira/browse/HDFS-12066
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs
>    Affects Versions: 3.0.0-alpha3
>            Reporter: lufei
>            Assignee: lufei
>              Labels: hdfs-ec-3.0-nice-to-have
>         Attachments: HDFS-12054.002.patch, HDFS-12066.001.patch
>
>
> FSNamesystem#removeErasureCodingPolicy should call checkNameNodeSafeMode() to 
> ensure Namenode is not in safemode



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to