[
https://issues.apache.org/jira/browse/TS-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416378#comment-13416378
]
Leif Hedstrom commented on TS-1348:
-----------------------------------
I think I have an idea. Setting these active timeouts also cancels the old
timeout, which could otherwise trigger while we are in KA. What we really need
is to replace these two active timeouts with a call to simply cancel the old
ones.
> replace keepalive connection timeout handle from set_active_timeout to
> set_inactivity_timeout
> ---------------------------------------------------------------------------------------------
>
> Key: TS-1348
> URL: https://issues.apache.org/jira/browse/TS-1348
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core, Network, Performance
> Affects Versions: 3.2.0
> Reporter: kuotai
> Assignee: kuotai
> Fix For: 3.3.0
>
> Attachments: kpa_timeout.patch
>
>
> if calling set_active_timeout function in keepalive, every connection will
> create one event and schedule in event system. so if having more and more
> connection in keepalive state(more and more event in schedule system), system
> have to take more time to PriorityEventQueue::check_ready.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
