[
https://issues.apache.org/jira/browse/AMBARI-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909470#comment-14909470
]
Hudson commented on AMBARI-13248:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3528 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3528/])
AMBARI-13248: Parallel library should process all futures even if one of them
throws an exception (jluniya) (jluniya:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=474e40862f0e66d12d333d83509453ab5c8728e6)
* ambari-server/src/main/java/org/apache/ambari/server/utils/Parallel.java
* ambari-server/src/test/java/org/apache/ambari/server/utils/TestParallel.java
> Parallel library should process all futures even if one of them throws an
> exception
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-13248
> URL: https://issues.apache.org/jira/browse/AMBARI-13248
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Affects Versions: 2.1.2
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Priority: Blocker
> Fix For: 2.1.2
>
>
> - Parallel library should process all futures even if one of them throws an
> exception
> - Consider the case where we spawn 1000 future requests and the very 1st
> thread throws an exception.
> - Since the exception handling is outside the for loop we would end up
> returning a result with all nulls to the caller.
> - In getStagesInProgress() as a fall back we check the ParallelLoopResult and
> get all the missing results sequentially, so this could lead to the main
> thread and the spawned threads will process same requests in parallel and
> could lead to issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
