You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Ho (JIRA)" <ji...@apache.org> on 2018/03/29 20:12:00 UTC

[jira] [Resolved] (IMPALA-2567) KRPC milestone 1

     [ https://issues.apache.org/jira/browse/IMPALA-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Ho resolved IMPALA-2567.
--------------------------------
    Resolution: Fixed

> KRPC milestone 1
> ----------------
>
>                 Key: IMPALA-2567
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2567
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Distributed Exec
>    Affects Versions: Impala 2.2.4
>            Reporter: Henry Robinson
>            Assignee: Michael Ho
>            Priority: Critical
>              Labels: scalability
>             Fix For: Impala 3.0, Impala 2.12.0
>
>
> Impala relies on Thrift 0.9.X for its RPC implementation. This is a venerable release and is showing its age. Problems include:
> * Low-quality SASL support (that we implemented ourselves)
> * Lack of high-quality nonblocking server ({{TNonBlockingServer}} is ok, but doesn't work with SASL, making it a non-starter for us. It is also very hard to provide support for sessions with {{TNonBlockingServer}}).
> * Lack of 0-copy native bytes type, meaning that large data structures are inefficient to send
> * Lack of support for async. server implementation, so expensive RPCs can consume threads that could have been used by cheap ones.
> Both [Kudu|https://github.com/cloudera/kudu/tree/master/src/kudu/rpc] and [fbthrift|https://github.com/facebook/fbthrift/blob/master/thrift/doc/Cpp2.md] have RPC implementations that address some or all of these shortcomings. We should evaluate both and commit to moving our RPC stack to one or the other.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)