You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2015/02/26 15:06:04 UTC
[jira] [Updated] (TS-3413) High CPU utilization when processing
Http/2 traffic
[ https://issues.apache.org/jira/browse/TS-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Susan Hinrichs updated TS-3413:
-------------------------------
Description:
Running ATS in forward transparent mode with Http/2 support enabled. After a few page views, ATS gets into a state where it is consistently using more than 100% CPU. I think what is happening is that the origin server is closing the connection (we get a TS_EVENT_VCONN_EOS in FetchSM). FetchSM sends a BODY_DONE to Http2ClientSession but the http_vc (origin socket?) is never closed, so with each poll interval the EOS is reported again and again.
was:
This was discovered while tracking the segmentation fault in TS-3405 and the original discussion is there.
Running ATS in forward transparent mode with Http/2 support enabled. After a few page views, ATS gets into a state where it is consistently using more than 100% CPU. I think what is happening is that the origin server is closing the connection (we get a TS_EVENT_VCONN_EOS in FetchSM). FetchSM sends a BODY_DONE to Http2ClientSession but the http_vc (origin socket?) is never closed, so with each poll interval the EOS is reported again and again.
> High CPU utilization when processing Http/2 traffic
> ---------------------------------------------------
>
> Key: TS-3413
> URL: https://issues.apache.org/jira/browse/TS-3413
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2, Performance
> Reporter: Susan Hinrichs
>
> Running ATS in forward transparent mode with Http/2 support enabled. After a few page views, ATS gets into a state where it is consistently using more than 100% CPU. I think what is happening is that the origin server is closing the connection (we get a TS_EVENT_VCONN_EOS in FetchSM). FetchSM sends a BODY_DONE to Http2ClientSession but the http_vc (origin socket?) is never closed, so with each poll interval the EOS is reported again and again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)