[
https://issues.apache.org/jira/browse/SLIDER-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193856#comment-14193856
]
Jonathan Maron commented on SLIDER-594:
---------------------------------------
I'd agree that a SLIDER-78 based approach may work best, i.e. introduce the
least amount of complexity/errors. However, it's unclear to me whether the AM
can recognize a container allocation as a restart? Should the delay be
introduced during the failure handling rather than the new container launch?
> Add a sleep before container restart as ports may not be released from the
> last activation
> ------------------------------------------------------------------------------------------
>
> Key: SLIDER-594
> URL: https://issues.apache.org/jira/browse/SLIDER-594
> Project: Slider
> Issue Type: Bug
> Components: agent-provider
> Affects Versions: Slider 0.50
> Reporter: Sumit Mohanty
> Assignee: Jonathan Maron
> Priority: Critical
> Fix For: Slider 0.60
>
>
> This is critical for applications that do not use dynamic port and
> applications using labels do not use dynamic ports. A configurable delay
> should be added to allow for scenarios where component instances get killed
> rather than stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
