[
https://issues.apache.org/jira/browse/THRIFT-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932780#comment-16932780
]
Qinghui Xu edited comment on THRIFT-4958 at 9/18/19 7:58 PM:
-------------------------------------------------------------
My theory/guess is that the thrift server is over loaded, and the requests
start to pile up after some time, and starting from some point clients time out
before the requests get processed. But if such theory is true, you should
witness that the client latency become bigger and bigger before eventual
timeout.
But this is only a speculation, without more information we cannot be more
helpful. Here are some questions you might want to answer:
* What's the setup of the server? (heap size, thread pool size, number of cpu)
* What's the resource usage on your server host/container? (cpu, memory,
network, etc)
* What's the load on the server? (number of concurrent connection, qps,
average response time, etc)
Eventually you might want to make a thread dump (or heap dump) of the server
when the latency issue happens.
was (Author: q.xu):
My theory/guess is that the thrift server is over loaded, and the requests
start to pile up after some time, and starting from some point clients time out
before the requests get processed. But if such theory is true, you should
witness that the client latency become bigger and bigger before eventual
timeout.
But this is only a speculation, without more information we cannot be more
helpful. Here are some
* What's the setup of the server? (heap size, thread pool size, number of cpu)
* What's the resource usage on your server host/container? (cpu, memory,
network, etc)
* What's the load on the server? (number of concurrent connection, qps,
average response time, etc)
Eventually you might want to make a thread dump (or heap dump) of the server
when the latency issue happens.
> TSocket: timed out reading 4 bytes from server:port
> ----------------------------------------------------
>
> Key: THRIFT-4958
> URL: https://issues.apache.org/jira/browse/THRIFT-4958
> Project: Thrift
> Issue Type: Bug
> Components: PHP - Library
> Affects Versions: 0.12.0
> Environment: Thrift 0.12: PHP 7.3 with Apache 2.4 on Ubuntu 18.04 ,
> Oracle JDK 8
> Reporter: Dedipyaman Das
> Priority: Critical
> Labels: bug
> Attachments: e.bmp
>
>
> I have come this error across on my development server while working on a PHP
> 7.3 client and Java 8 Server.
> *TSocket: timed out reading 4 bytes from server*:port
> The PHP client is using TFramedTransport with Binary Protocol and the Java
> server is using TThreadSelectorServer. The error appeared all of a sudden and
> doesn't go away unless I restart the server, and it comes back after a while.
> This issue seems to have been raised at:
> https://issues.apache.org/jira/browse/THRIFT-347 and fixed for version 0.6,
> but it seems to occur for me on version 0.12 - for reasons I don't know.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
