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

Hadoop QA commented on HDFS-10614:
----------------------------------

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


This message was automatically generated.



> Appended blocks can be closed even before IBRs from DataNodes
> -------------------------------------------------------------
>
>                 Key: HDFS-10614
>                 URL: https://issues.apache.org/jira/browse/HDFS-10614
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-10614.01.patch, HDFS-10614.02.patch, 
> HDFS-10614.03.patch
>
>
> Scenario:
>    1. Open the file for append()
>    2. Trigger append pipeline setup by adding some data.
>    3. Consider RECEIVING IBRs of DNs reaches NN first.
>    4. updatePipeline() rpc sent to namenode to update the pipeline.
>    5. Now, if complete() is called on the file even before closing the 
> pipeline, then block will be COMPLETE, even before block is actually 
> FINALIZED at DN side and file will be closed.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to