[
https://issues.apache.org/jira/browse/IMPALA-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Riza Suminto resolved IMPALA-11548.
-----------------------------------
Fix Version/s: Impala 4.2.0
Resolution: Fixed
The fix has been merged
https://gerrit.cloudera.org/#/c/18938/
> TTransportException can be thrown for RPC connection that is open for long
> time
> -------------------------------------------------------------------------------
>
> Key: IMPALA-11548
> URL: https://issues.apache.org/jira/browse/IMPALA-11548
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.2.0
> Reporter: Riza Suminto
> Assignee: Riza Suminto
> Priority: Major
> Fix For: Impala 4.2.0
>
>
> After Impala upgrade CPP thrift version to 0.16.0, we are seeing
> TTransportException thrown for RPC connection that is open for long time.
> thrift-0.16.0 add counter to limit message size at
> [https://github.com/apache/thrift/commit/63213c1].
> The TTransportException is thrown when remainingMessageSize < numBytes,
> indicating that TTransport was not flushed properly.
> This is presumably due to the fact that both input_ and output_ TProtocol
> within TAcceptQueueServer::Task has different TTransport object within them.
> Letting both input_ and output_to share the same TTransport object might fix
> the flushing mechanism and properly reset the limit counter of the shared
> TTransport.
> See:
> [https://github.com/apache/impala/blob/fec7a79c50de9ef5db2c652ece111aaa303d57c7/be/src/transport/TSaslServerTransport.cpp#L132-L146]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
