[
https://issues.apache.org/jira/browse/TS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240109#comment-14240109
]
Eric Schwartz commented on TS-1461:
-----------------------------------
I am working on this now. I think the upper limit on restart time seems
reasonable but was wondering if I could get some clarification re: exponential
backoff vs # of restarts. I think it definitely makes sense to have it do
exponential backoff up to some upper limit but once we reach that limit do we
wish to continue attempting to restart or after we get to the point where we've
waited 60 seconds for a restart do we want that to be our last attempt?
It looks like David's initial concern wouldn't be solved unless we have a limit
on the # of times we restart in addition to doing exponential backoff for time
between restarts. What do we think would be a reasonable # of attempts?
> traffic_manager should only try X number of times to start traffic_server
> -------------------------------------------------------------------------
>
> Key: TS-1461
> URL: https://issues.apache.org/jira/browse/TS-1461
> Project: Traffic Server
> Issue Type: Improvement
> Components: Manager
> Affects Versions: 3.2.0
> Reporter: David Carlin
> Assignee: Eric Schwartz
> Priority: Minor
> Fix For: 5.3.0
>
>
> If there is a problem with the config and traffic_server doesn't start,
> traffic_manager still tries indefinitely to restart ATS. This fills up the
> TS logs, /var/log/messages, and can send out hundreds of emails via
> proxy.config.alarm_email.
> Is it possible to have traffic_manager only attempt X number of restarts? Or
> X number of restarts in a given period of time?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
