[
https://issues.apache.org/jira/browse/HADOOP-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994215#comment-14994215
]
Steve Loughran commented on HADOOP-11684:
-----------------------------------------
Aaron - We are having jenkins problems, with (a) stability and (b) people
caring about they've just broken the build.
How to tell
# if you look at >1 jenkins patch runs you learn to recognise which tests are
unreliable right now
# https://builds.apache.org/view/H-L/view/Hadoop/ gives you the overall view
# given the location of a patch, anything which only touches a single module is
likely to have no impact on modules other than it and its direct/indirect
dependencies.
Here it was clear that the test runs had to be unrelated (we all hate
ZKFailover controller), but javadoc was something else
> S3a to use thread pool that blocks clients
> ------------------------------------------
>
> Key: HADOOP-11684
> URL: https://issues.apache.org/jira/browse/HADOOP-11684
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.7.0
> Reporter: Thomas Demoor
> Assignee: Thomas Demoor
> Fix For: 2.8.0, 3.0.0
>
> Attachments: HADOOP-11684-001.patch, HADOOP-11684-002.patch,
> HADOOP-11684-003.patch, HADOOP-11684-004.patch, HADOOP-11684-005.patch,
> HADOOP-11684-006.patch
>
>
> Currently, if fs.s3a.max.total.tasks are queued and another (part)upload
> wants to start, a RejectedExecutionException is thrown.
> We should use a threadpool that blocks clients, nicely throtthling them,
> rather than throwing an exception. F.i. something similar to
> https://github.com/apache/incubator-s4/blob/master/subprojects/s4-comm/src/main/java/org/apache/s4/comm/staging/BlockingThreadPoolExecutorService.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
