[
https://issues.apache.org/jira/browse/MAPREDUCE-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210934#comment-13210934
]
Steve Loughran commented on MAPREDUCE-3877:
-------------------------------------------
I'm going to note that these tests show flaws in the current lifecycle that
need to be addressed. Specifically
# as the ensureState checks are performed at the end of all subclasses
start/stop/init operations, they always perform their operations regardless of
the current state. This allows you to enter these states more than once
# if anything goes wrong during init and start the system is left in an
indeterminate state
# you can't stop without starting, yet init can acquire resources that need to
be explicitly released -and which you may want to release without starting the
service.
> Add a test to formalise the current state transitions of the yarn lifecycle
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-3877
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3877
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: mrv2
> Affects Versions: 0.24.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.24.0, 0.23.2
>
> Attachments: MAPREDUCE-3877.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Add a test service that counts the number of times it's state methods are
> called; and can be set to raise an exception on any such entry. Use it to
> show what the current lifecycle state model is, so that unintentional
> regressions can be detected.
> It will also act as a foundation for intentional changes to that lifecycle
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
