You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficserver.apache.org by Karthik Kailash <ka...@gmail.com> on 2015/06/11 00:54:20 UTC

Behavior of traffic server on client connection timeout?

Hi,

I have ATS 4.2 configured as a reverse proxy for a HTTP upload service.
The flow is ATS -> HAProxy -> Origin server farm.

In records.config, I have:
CONFIG proxy.config.http.transaction_no_activity_timeout_in INT 60
CONFIG proxy.config.http.transaction_no_activity_timeout_out INT 60

Which I assume governs ATS behavior when there's been no activity (no new
bytes from user connection).

I did a test where the client connection is interrupted (by unplugging the
ethernet cable during an upload).  However, ATS log does not show a timeout
after 60 seconds.  Instead, once the upstream server detects a connection
timeout, it returns a 500, which gets logged by ATS.

I'd like to have ATS detect a client connection timeout, and then terminate
its connection to the origin server and log the event.  How can I do this?

-- 
Karthik Kailash
Phone: (408) 768-7704

Re: Behavior of traffic server on client connection timeout?

Posted by Sudheer Vinukonda <su...@yahoo-inc.com>.
Also, note that ATS's implementation cancels the UA (client) side inactivity timer once the origin servers headers have been received. Perhaps, this may be what you are noticing. 


     On Wednesday, June 10, 2015 4:05 PM, Sudheer Vinukonda <su...@yahoo-inc.com> wrote:
   

 <proxy.config.http.transaction_no_activity_timeout_out> is the inactivity timeout on the outbound side (ATS to origin connection). Perhaps, in your test, since both the outbound and inbound are configured as 60 sec, the origin side (HA Proxy) may be occurring faster. You may want to set the origin side timer to higher than 60 sec and check.
Thanks,
Sudheer  


     On Wednesday, June 10, 2015 3:55 PM, Karthik Kailash <ka...@gmail.com> wrote:
   

 Hi,

I have ATS 4.2 configured as a reverse proxy for a HTTP upload service.  The flow is ATS -> HAProxy -> Origin server farm.

In records.config, I have:
CONFIG proxy.config.http.transaction_no_activity_timeout_in INT 60
CONFIG proxy.config.http.transaction_no_activity_timeout_out INT 60

Which I assume governs ATS behavior when there's been no activity (no new bytes from user connection).  

I did a test where the client connection is interrupted (by unplugging the ethernet cable during an upload).  However, ATS log does not show a timeout after 60 seconds.  Instead, once the upstream server detects a connection timeout, it returns a 500, which gets logged by ATS.

I'd like to have ATS detect a client connection timeout, and then terminate its connection to the origin server and log the event.  How can I do this?

-- 
Karthik Kailash
Phone: (408) 768-7704

   

  

Re: Behavior of traffic server on client connection timeout?

Posted by Sudheer Vinukonda <su...@yahoo-inc.com>.
<proxy.config.http.transaction_no_activity_timeout_out> is the inactivity timeout on the outbound side (ATS to origin connection). Perhaps, in your test, since both the outbound and inbound are configured as 60 sec, the origin side (HA Proxy) may be occurring faster. You may want to set the origin side timer to higher than 60 sec and check.
Thanks,
Sudheer  


     On Wednesday, June 10, 2015 3:55 PM, Karthik Kailash <ka...@gmail.com> wrote:
   

 Hi,

I have ATS 4.2 configured as a reverse proxy for a HTTP upload service.  The flow is ATS -> HAProxy -> Origin server farm.

In records.config, I have:
CONFIG proxy.config.http.transaction_no_activity_timeout_in INT 60
CONFIG proxy.config.http.transaction_no_activity_timeout_out INT 60

Which I assume governs ATS behavior when there's been no activity (no new bytes from user connection).  

I did a test where the client connection is interrupted (by unplugging the ethernet cable during an upload).  However, ATS log does not show a timeout after 60 seconds.  Instead, once the upstream server detects a connection timeout, it returns a 500, which gets logged by ATS.

I'd like to have ATS detect a client connection timeout, and then terminate its connection to the origin server and log the event.  How can I do this?

-- 
Karthik Kailash
Phone: (408) 768-7704