[
https://issues.apache.org/jira/browse/IMPALA-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailesh Mukil resolved IMPALA-3977.
-----------------------------------
Resolution: Won't Fix
We're going ahead with KuduRPC, tracked by IMPALA-2567, so we won't fix this
JIRA which is targeted specifically for Thrift, as that will be deprecated for
internal communication in the near future.
> TransmitData() should not block.
> --------------------------------
>
> Key: IMPALA-3977
> URL: https://issues.apache.org/jira/browse/IMPALA-3977
> Project: IMPALA
> Issue Type: Improvement
> Components: Distributed Exec
> Affects Versions: Impala 2.7.0
> Reporter: Henry Robinson
> Assignee: Sailesh Mukil
> Labels: rpc
>
> {{TransmitData()}} calls effectively block until an error occurs (e.g.
> {{datastream_sender_timeout_ms}} expires) or the RPC is serviced by the
> receiver.
> This is bad for a variety of reasons, not least that it makes it impossible
> to cancel the sender without also cancelling the recipient (who might not
> even be running!).
> Instead, we should have {{TransmitData()}} return control to the caller with
> an {{EAGAIN}}-like error so that the row batch can be resent in the future if
> the caller decides to do so.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
