[
https://issues.apache.org/jira/browse/TS-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416386#comment-13416386
]
Leif Hedstrom commented on TS-1348:
-----------------------------------
So, looking some more, are you positive removing the first activity timeout is
correct? I'm thinking a patch more like
{code}
diff --git a/proxy/http/HttpClientSession.cc b/proxy/http/HttpClientSession.cc
index 188e785..bf361c0 100644
--- a/proxy/http/HttpClientSession.cc
+++ b/proxy/http/HttpClientSession.cc
@@ -155,7 +155,6 @@ HttpClientSession::new_transaction()
DebugSsn("http_cs", "[%" PRId64 "] using accept inactivity timeout
[%"PRId64" seconds]",
con_id, HttpConfig::m_master.accept_no_activity_timeout);
client_vc->set_inactivity_timeout(HRTIME_SECONDS(HttpConfig::m_master.accept_no_activity_timeout));
-
client_vc->set_active_timeout(HRTIME_SECONDS(HttpConfig::m_master.transaction_active_timeout_in));
transact_count++;
@@ -630,7 +629,7 @@ HttpClientSession::release(IOBufferReader * r)
ka_vio = this->do_io_read(this, INT64_MAX, read_buffer);
ink_assert(slave_ka_vio != ka_vio);
client_vc->set_inactivity_timeout(HRTIME_SECONDS(ka_in));
- client_vc->set_active_timeout(HRTIME_SECONDS(ka_in));
+ client_vc->cancel_active_timeout();
}
}
{code}
> 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
