[
https://issues.apache.org/jira/browse/TS-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167040#comment-14167040
]
James Peach commented on TS-3119:
---------------------------------
These are the socket option parameters we support:
{code}
proxy.config.cluster.sock_option_flag
proxy.config.cluster.sock_packet_mark
proxy.config.cluster.sock_packet_tos
proxy.config.net.sock_mss_in
proxy.config.net.sock_option_flag_in
proxy.config.net.sock_option_flag_out
proxy.config.net.sock_packet_mark_in
proxy.config.net.sock_packet_mark_out
proxy.config.net.sock_packet_tos_in
proxy.config.net.sock_packet_tos_out
proxy.config.net.sock_recv_buffer_size_in
proxy.config.net.sock_recv_buffer_size_out
proxy.config.net.sock_send_buffer_size_in
proxy.config.net.sock_send_buffer_size_out
{code}
This patch adds {{proxy.config.net.sock_option_linger_enabled_out}} and
{{proxy.config.net.sock_option_linger_timeout_out}}, which seem like they
should only apply to origin server connections. I don't think you need an
"enabled" flag and a timeout ... doesn't setting a timeout imply that it should
be enabled?
> Add option to support SO_LINGER to origin server
> ------------------------------------------------
>
> Key: TS-3119
> URL: https://issues.apache.org/jira/browse/TS-3119
> Project: Traffic Server
> Issue Type: Improvement
> Components: Network
> Reporter: kang li
> Fix For: 5.2.0
>
> Attachments: linger.diff
>
>
> When install ATS and apache in the same box to do SSL termination. We saw
> port exhaustion, performance drop and request missing through ATS.
> Before migration we are using stunnel to do SSL termination. There were no
> such problem. After investigation we found add SO_LINGER option to origin
> could resolve these problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
