[ https://issues.apache.org/jira/browse/TS-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371597#comment-14371597 ]
Bryan Call commented on TS-3364: -------------------------------- [~sudheerv] Looks like everything has been committed, can this be marked as resolved? > Add command line config validation support to traffic_server > ------------------------------------------------------------ > > 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 > Assignee: Sudheer Vinukonda > Fix For: 6.0.0 > > > 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.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} > Based on concerns expressed, it has been agreed to not change the > traffic_server's behavior to loading with fatal config. Instead, this jira > will be used to add a command line option to traffic_server to load and > validate the config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)