You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (JIRA)" <ji...@apache.org> on 2019/06/26 20:52:00 UTC
[jira] [Commented] (THRIFT-4898) Pipe write operations across a
network are limited to 65,535 bytes per write.
[ https://issues.apache.org/jira/browse/THRIFT-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873652#comment-16873652 ]
Jens Geyer commented on THRIFT-4898:
------------------------------------
Larger writes across a non-localhost pipe will reproducibly hang/timeout the communication on the other end.
> Pipe write operations across a network are limited to 65,535 bytes per write.
> ------------------------------------------------------------------------------
>
> Key: THRIFT-4898
> URL: https://issues.apache.org/jira/browse/THRIFT-4898
> Project: Thrift
> Issue Type: Bug
> Components: netstd - Library
> Reporter: Jens Geyer
> Assignee: Jens Geyer
> Priority: Major
> Fix For: 0.13.0
>
>
> {quote}Pipe write operations across a network are limited to 65,535 bytes per write. For more information regarding pipes, see the Remarks section.{quote}
> Source: [WriteFileEx function|https://msdn.microsoft.com/en-us/library/windows/desktop/aa365748(v=vs.85).aspx]
> I managed to run into exactly that limit today. Patch follows.
> Symptom is that
> * the writing end acts as if it had written all the bytes (in fact, it did)
> * but the remainder of ~ 65535 bytes is just lost somewhere and never reaches the reading end
> Consequently, the process at the reading end of the pipe gets stuck while waiting for the remaining bytes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)