[
https://issues.apache.org/jira/browse/SLIDER-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193855#comment-14193855
]
Steve Loughran commented on SLIDER-594:
---------------------------------------
may relate to SLIDER-78; which suggested a programmable delay before reacting
to any container loss event (essentially delaying the (queued) reporting of it).
This doesn't handle flex down/up pairs, or full cluster stop/start. Maybe the
agent could know of ports to probe for open-ness and pause until they are
ready. Though if the process at the end of the port is hung, that would hang
the agent, and lead to other problems
> 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)
