Skip to content
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.

--timeout is not respected #131

Open
blampe opened this issue Jun 28, 2016 · 4 comments
Open

--timeout is not respected #131

blampe opened this issue Jun 28, 2016 · 4 comments

Comments

@blampe
Copy link
Contributor

blampe commented Jun 28, 2016

tcurl -p localhost:44390 foo --timeout 500000 --health
NOT OK
TchannelConnectionTimeoutError: connection timed out after 2001ms (limit was 2000ms)
@blampe
Copy link
Contributor Author

blampe commented Jun 28, 2016

@kriskowal have you seen this before?

@Raynos
Copy link
Contributor

Raynos commented Jun 28, 2016

connection timeout is different and not configurable.

There are two timeouts.

  • init handshake of the tchannel protocol must finished in 2 seconds (aka timeout for init response)
  • rpc request must finish within --timeout time, ( aka timeout for call response ).

If the init handshake times out that generally means that the TCP connection was opened but the remote side did not speak the tchannel protocol ( HTTP server ? )

Other reasons why the init handshake fails is

  • a fatal exception in the remote server, it will never respond
  • a bug in the tchannel server library
  • trying to make a request to a 100% CPU process

@ctrlhxj
Copy link

ctrlhxj commented Jun 28, 2016

The server is speaking tchannel and it's a local process, which means that it's either

  • a bug on server side (possible but unlikely since the server is running fine)
    or
  • make request to 100% CPU process: could you clarify a bit on this? 100% means 1 core or all cores on the server?

@prashantv
Copy link
Contributor

@ctrlhxj You can try using tcap to help diagnose what's going on.

If you really want to have a much higher timeout for a connection, you can also try using yab which uses the specified timeout for connecting as well as the request.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants