You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Brown (JIRA)" <ji...@apache.org> on 2017/04/14 00:03:42 UTC

[jira] [Commented] (CASSANDRA-10735) Support netty openssl (netty-tcnative) for client encryption

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

Jason Brown commented on CASSANDRA-10735:
-----------------------------------------

Once CASSANDRA-8457 is commited, this will be very easy to me to do (especially as the changes to {{SSLFactory}} in CASSANDRA-8457 will have 90% of the functionality needed here)

> Support netty openssl (netty-tcnative) for client encryption
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-10735
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10735
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Andy Tolbert
>            Assignee: Jason Brown
>             Fix For: 4.0
>
>         Attachments: nettysslbench.png, nettysslbench_small.png, nettyssl-bench.tgz, netty-ssl-trunk.tgz, sslbench12-03.png
>
>
> The java-driver recently added support for using netty openssl via [netty-tcnative|http://netty.io/wiki/forked-tomcat-native.html] in [JAVA-841|https://datastax-oss.atlassian.net/browse/JAVA-841], this shows a very measured improvement (numbers incoming on that ticket).   It seems likely that this can offer improvement if implemented C* side as well.
> Since netty-tcnative has platform specific requirements, this should not be made the default, but rather be an option that one can use.



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