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

Hadoop QA commented on HDFS-15856:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime ||  Logfile || 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 21s{color} 
|  | {color:red} https://github.com/apache/hadoop/pull/2721 does not apply to 
trunk. Rebase required? Wrong Branch? See 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute for help. 
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| GITHUB PR | https://github.com/apache/hadoop/pull/2721 |
| JIRA Issue | HDFS-15856 |
| Console output | 
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2721/11/console |
| versions | git=2.17.1 |
| Powered by | Apache Yetus 0.13.0 https://yetus.apache.org |


This message was automatically generated.



> Make recover the pipeline in same packet exceed times for stream closed 
> configurable.
> -------------------------------------------------------------------------------------
>
>                 Key: HDFS-15856
>                 URL: https://issues.apache.org/jira/browse/HDFS-15856
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Qi Zhu
>            Assignee: Qi Zhu
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Now recover the pipeline five times in a row for the same packet, will close 
> the stream, but i think it should be configurable for different cluster 
> needed.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to