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

Jason Brown commented on CASSANDRA-8457:
----------------------------------------

Addressed a few problems due to failing dtests. The currently failing utests 
and dtests are almost *all* related to streaming; I'm working on the few 
remaining dtests.

* correctly handle canceled futures in 
{{OutboundMessagingConnection#handleMessageFuture}}
* Fixed NPE in {{OutboundMessagingConnection#reconnectWithNewIp}}
* refactored some code wrt outbound connection creation
* added package-level documentation, primarily describing the handshake and 
messaging format

Also, I have a patched version of netty 4.1.6 in this branch that fixes a flush 
problem in {{LZ4FrameEncoder}}. Netty folks are reviewing now, and will 
hopefully get an updated netty lib soon.

[~slebresne] ready for your next round of comments when you have time :)

> nio MessagingService
> --------------------
>
>                 Key: CASSANDRA-8457
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8457
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jonathan Ellis
>            Assignee: Jason Brown
>            Priority: Minor
>              Labels: netty, performance
>             Fix For: 4.x
>
>
> Thread-per-peer (actually two each incoming and outbound) is a big 
> contributor to context switching, especially for larger clusters.  Let's look 
> at switching to nio, possibly via Netty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to