[ 
https://issues.apache.org/jira/browse/TS-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304094#comment-14304094
 ] 

Sudheer Vinukonda edited comment on TS-3364 at 2/3/15 10:00 PM:
----------------------------------------------------------------

Yeah, I agree with the concern - the reason for this jira is to basically allow 
for automatically updating configuration via some sort of control plane, while 
minimizing the impact due to errors in the configuration. I will generate error 
logs to report the failures with setting *1* and *2*. 

The default value for the setting will remain *0* (at least, until 6.0) to 
ensure backward compatibility with current behavior.


was (Author: sudheerv):
Yeah, I agree with the concern - the reason for this jira is to basically allow 
for automatically updating configuration via some sort of control plane, while 
minimizing the impact due to errors in the configuration. I will generate error 
logs to report the failures with setting *1* and *2*. 

> Add configuration to control traffic_server's reaction to fatal errors  
> during (re)loading the config files.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: TS-3364
>                 URL: https://issues.apache.org/jira/browse/TS-3364
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 5.3.0
>            Reporter: Sudheer Vinukonda
>
> Currently, traffic_server fails to initialize when it encounters fatal errors 
> in loading the config files during start up. During dynamic reloading of 
> config files (e.g. via traffic_line), traffic_server rejects new config and 
> falls back to existing/old config (however, if there was a traffic_server 
> crash/restart subsequently, that can again result into failing to initialize).
> This jira proposes to make the behavior of traffic_server when it encounters 
> such fatal errors configurable via a new setting 
> {{proxy.config.url_remap.ignore_fatal_errors}} with the below options:
> {code}
> 0 : All errors are fatal, do not load/reload
> 1 : Ignore a bad config line, continue with the rest
> 2 : Ignore a bad config line, stop parsing the file further
> ..
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to