You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/05/20 13:16:38 UTC
[jira] [Assigned] (SLIDER-78) add a programmable delay before
re-issuing a request for a container after a failure
[ https://issues.apache.org/jira/browse/SLIDER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran reassigned SLIDER-78:
------------------------------------
Assignee: Sumit Mohanty
This is low priority, its just something we need to think about: having agents be able to wait configurable time before execing the real code. This could be a simple as inserting a sleep into the command sequence (in which case it could perhaps be added to the individual .py scripts & documented)
> add a programmable delay before re-issuing a request for a container after a failure
> ------------------------------------------------------------------------------------
>
> Key: SLIDER-78
> URL: https://issues.apache.org/jira/browse/SLIDER-78
> Project: Slider
> Issue Type: Sub-task
> Components: appmaster
> Reporter: Steve Loughran
> Assignee: Sumit Mohanty
> Priority: Minor
>
> A failure mode that surfaces is restarting a cluster immediately after freezing it. The port the HBase master wanted had not yet been released by the OS, so it failed when trying to listen on it -repeatedly.
> Having a delay on execing the actual binary (i.e. get the container, but insert a sleep) would address this
--
This message was sent by Atlassian JIRA
(v6.2#6252)