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

Hadoop QA commented on HDFS-9105:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  18m 45s | Pre-patch trunk compilation is 
healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any 
@author tags. |
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear 
to include any new or modified tests.  Please justify why no new tests are 
needed for this patch. Also please list what manual steps were performed to 
verify this patch. |
| {color:green}+1{color} | javac |   9m 25s | There were no new javac warning 
messages. |
| {color:green}+1{color} | javadoc |  11m 43s | There were no new javadoc 
warning messages. |
| {color:green}+1{color} | release audit |   0m 23s | The applied patch does 
not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle |   1m 38s | The applied patch generated  6 
new checkstyle issues (total was 561, now 566). |
| {color:red}-1{color} | whitespace |   0m  0s | The patch has 1  line(s) that 
end in whitespace. Use git apply --whitespace=fix. |
| {color:green}+1{color} | install |   1m 44s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 39s | The patch built with 
eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   2m 58s | The patch does not introduce 
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | native |   4m  6s | Pre-build of native portion |
| {color:red}-1{color} | hdfs tests | 132m 17s | Tests failed in hadoop-hdfs. |
| | | 183m 42s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.hdfs.server.blockmanagement.TestBlockManager |
|   | hadoop.hdfs.web.TestWebHDFSOAuth2 |
|   | hadoop.hdfs.server.namenode.TestCacheDirectives |
| Timed out tests | org.apache.hadoop.hdfs.server.namenode.TestAuditLogger |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12761135/HDFS-9105.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 3f42753 |
| checkstyle |  
https://builds.apache.org/job/PreCommit-HDFS-Build/12541/artifact/patchprocess/diffcheckstylehadoop-hdfs.txt
 |
| whitespace | 
https://builds.apache.org/job/PreCommit-HDFS-Build/12541/artifact/patchprocess/whitespace.txt
 |
| hadoop-hdfs test log | 
https://builds.apache.org/job/PreCommit-HDFS-Build/12541/artifact/patchprocess/testrun_hadoop-hdfs.txt
 |
| Test Results | 
https://builds.apache.org/job/PreCommit-HDFS-Build/12541/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf900.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP 
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/12541/console |


This message was automatically generated.

> separate replication config for client to create a file or set replication
> --------------------------------------------------------------------------
>
>                 Key: HDFS-9105
>                 URL: https://issues.apache.org/jira/browse/HDFS-9105
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: HDFS-9105.patch
>
>
> one scenario when we want this new config: we want to enforce min replication 
> of value 2, when client try to create a file, it's check against the 
> replication factor of the new config, which is set to 2,  so that client can 
> not create a file of replication of 1. But when client try to close file and 
> there are some datanode failures in the pipeline and only 1 datanode remain, 
> it is checked against old minReplication value, which has value 1, so we will 
> allow client to close the file.



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

Reply via email to