[
https://issues.apache.org/jira/browse/HADOOP-10085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887886#comment-13887886
]
Karthik Kambatla commented on HADOOP-10085:
-------------------------------------------
Reading through the issues addressed by YARN-117 and the related discussions, I
now see the reason behind the current approach of parent service entering a
state before child services. Agree we ll probably have to add transient states
like INITING, STARTING etc. to address to go the other way, and that it is too
large a change to just bring in.
I think there is merit to getting this patch in. Let me take a closer look at
the tests.
> CompositeService should allow adding services while being inited
> ----------------------------------------------------------------
>
> Key: HADOOP-10085
> URL: https://issues.apache.org/jira/browse/HADOOP-10085
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Reporter: Karthik Kambatla
> Assignee: Steve Loughran
> Attachments: HADOOP-10085-002.patch, HADOOP-10085-003.patch,
> HADOOP-10085-004.patch
>
>
> We can add services to a CompositeService. However, if we do that while
> initing the CompositeService, it leads to a ConcurrentModificationException.
> It would be nice to allow adding services even during the init of
> CompositeService.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
