You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/04/05 21:59:16 UTC

[jira] [Assigned] (TS-1804) fds_limit improperly set upon server reboot + ats restart

     [ https://issues.apache.org/jira/browse/TS-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom reassigned TS-1804:
---------------------------------

    Assignee: Leif Hedstrom
    
> fds_limit improperly set upon server reboot + ats restart
> ---------------------------------------------------------
>
>                 Key: TS-1804
>                 URL: https://issues.apache.org/jira/browse/TS-1804
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: David Carlin
>            Assignee: Leif Hedstrom
>
> proxy.config.net.connections_throttle = 70000 in records.config.
> /etc/security/limits.conf:
> * - nofile 500000
> When I reboot a server and start ATS, every time ATS will set fds_limit to value of proxy.config.net.connections_throttle instead of the per-user max set in limits.conf - it is my understanding it should pick limits.conf value if its higher.
> Subsequent restarts of ATS will always pick the limits.conf value, the problem only occurs when starting ATS after a server reboot.
> This was causing us to experience the error 'too many open file descriptors, emergency throttling' on random hosts that had too low a value for fds_limit.
> The workaround is to set proxy.config.net.connections_throttle higher or restart ATS twice upon server startup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira