[
https://issues.apache.org/jira/browse/CASSANDRA-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803136#action_12803136
]
Jonathan Ellis commented on CASSANDRA-705:
------------------------------------------
(3) I will code up the thread refactor then, I think that will deal with this
problem. Not having to worry about packet size limitations is a pretty good
reason to use TCP. (Although I haven't changed that yet, now that you mention
it. :)
> explore replacing socket nio with blocking io
> ---------------------------------------------
>
> Key: CASSANDRA-705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-705
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.6
>
> Attachments:
> 0001-make-shutdown-non-reentrant-and-make-MS-a-true-singlet.txt,
> 0002-replace-tcp-socket-reads-w-blocking-i-o.txt,
> 0003-replace-tcp-writes-w-blocking-i-o.txt,
> 0004-implement-streaming-w-blocking-io.txt,
> 0005-convert-gossip-to-use-tcp.-this-finishes-the-removal-o.txt,
> 0006-handle-node-failure.patch, 0007-simplify-header-code.patch,
> 0008-fix-streaming.patch
>
>
> MessagingService's nonblocking io has been a source of bugs both in our code
> and in the JVM in every release of Cassandra. Time to explore moving to
> blocking i/o, which is simpler, more robust (in terms of the JVM
> implementation), and possibly more performant as well
> (http://paultyma.blogspot.com/2008/03/writing-java-multithreaded-servers.html).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
