[
https://issues.apache.org/jira/browse/HDFS-8287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828972#comment-15828972
]
Hadoop QA commented on HDFS-8287:
---------------------------------
| (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-8287 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-8287 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12767729/HDFS-8287.15.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/18200/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> DFSStripedOutputStream.writeChunk should not wait for writing parity
> ---------------------------------------------------------------------
>
> Key: HDFS-8287
> URL: https://issues.apache.org/jira/browse/HDFS-8287
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: erasure-coding, hdfs-client
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Kai Sasaki
> Attachments: h8287_20150911.patch, HDFS-8287.12.patch,
> HDFS-8287.13.patch, HDFS-8287.14.patch, HDFS-8287.15.patch,
> HDFS-8287-HDFS-7285.00.patch, HDFS-8287-HDFS-7285.01.patch,
> HDFS-8287-HDFS-7285.02.patch, HDFS-8287-HDFS-7285.03.patch,
> HDFS-8287-HDFS-7285.04.patch, HDFS-8287-HDFS-7285.05.patch,
> HDFS-8287-HDFS-7285.06.patch, HDFS-8287-HDFS-7285.07.patch,
> HDFS-8287-HDFS-7285.08.patch, HDFS-8287-HDFS-7285.09.patch,
> HDFS-8287-HDFS-7285.10.patch, HDFS-8287-HDFS-7285.11.patch,
> HDFS-8287-HDFS-7285.WIP.patch, HDFS-8287-performance-report.pdf,
> jstack-dump.txt
>
>
> When a stripping cell is full, writeChunk computes and generates parity
> packets. It sequentially calls waitAndQueuePacket so that user client cannot
> continue to write data until it finishes.
> We should allow user client to continue writing instead but not blocking it
> when writing parity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
