hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17721) Provide streaming APIs with SSL/TLS
Date Fri, 03 Mar 2017 03:32:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893675#comment-15893675
] 

stack commented on HBASE-17721:
-------------------------------

We can't put up grpc on our rpc port. We want hbase-1.x clients able to talk to hbase-2.0.0.

Guava is a pain, yes, but we have a set of libs of this type -- i.e. critical libs that we
can't do without and currently can't update beyond the creaky old versions that hadoop runs
-- but we have to have fix general issue this so wouldn't worry about it. One concern is that
grpc needs pb3. HBase is pb2.5 (though we run a shaded pb3 internally).

Maybe the way to go is just put up a new port for now so you can play (which is sort of what
HBASE-8691 did). IIRC cockroachdb tried to be smart and run with one port only for webui and
data but had to give up on it (don't have my hand on the blog just now). We'll probably need
to do the same.

Yeah, playing w/ HBASE-13467 would be a good approach. The original patch is by the grpc fellows.
They might show up again if they see progress there.

I love this issue (again). Smile.

> Provide streaming APIs with SSL/TLS
> -----------------------------------
>
>                 Key: HBASE-17721
>                 URL: https://issues.apache.org/jira/browse/HBASE-17721
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Alex Araujo
>            Assignee: Alex Araujo
>             Fix For: 2.0.0
>
>
> Umbrella to add optional client/server streaming capabilities to HBase.
> This would allow bandwidth to be used more efficiently for certain operations, and allow
clients to use SSL/TLS for authentication and encryption.
> Desired client/server scaffolding:
> - HTTP/2 support
> - Protocol negotiation (blocking vs streaming, auth, encryption, etc.)
> - TLS/SSL support
> - Streaming RPC support
> Possibilities (and their tradeoffs):
> - gRPC: Some initial work and discussion on HBASE-13467 (Prototype using GRPC as IPC
mechanism)
> -- Has most or all of the desired scaffolding
> -- Adds additional g* dependencies. Compat story for g* dependencies not always ideal
> - Custom HTTP/2 based client/server APIs
> -- More control over compat story
> -- Non-trivial to build scaffolding; might reinvent wheels along the way
> - Others?
> Related Jiras that might be rolled in as sub-tasks (or closed/replaced with new ones):
> HBASE-17708 (Expose config to set two-way auth over TLS in HttpServer and add a test)
> HBASE-8691 (High-Throughput Streaming Scan API)
> HBASE-14899 (Create custom Streaming ReplicationEndpoint)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message