[
https://issues.apache.org/jira/browse/IMPALA-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v updated IMPALA-8420:
------------------------------
Component/s: Clients
> Support HTTP based HS2/beeswax endpoints on coordinators
> --------------------------------------------------------
>
> Key: IMPALA-8420
> URL: https://issues.apache.org/jira/browse/IMPALA-8420
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend, Clients
> Affects Versions: Impala 3.3.0
> Reporter: bharath v
> Priority: Major
>
> The ask is to support HTTP based endpoints for client <-> coordinator
> communication.
> Currently they are implemented as thrift over binary. With this, the
> coordinator can support client reconnects (incase of flaky clients) and also
> opens up the possibility to use smarter L7 load balancers instead of relying
> on L4 load balancers using IP hashing.
> Some notes (based on my research so far)
> - Thrift supports THttpTransport but cookie support is unclear
> - We need to rethink the server side session management a bit, since the
> current session handling is tied to the connection. If a connection is
> closed, server side session is wiped off. We need to decouple both to support
> reconnects.
> - Current query lifecycle is tied to the client since the coordinator expects
> the client to drain the current result set row batch before producing the
> next one. If reconnects are supported, coordinator needs to aggressively
> materialize result set so that the resources are not held for longer while
> waiting for the client to reconnect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
