[jira] Commented: (CASSANDRA-728) refactor blocking io to use thread (and queue) per conn pool, not thread per socket

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-728:
------------------------------------------

note that we don't have to null out old OTCs anymore from pool.reset(), since a closed OTC will automatically reconnect if/when write() is called again.

no attempt is made to clear out pool entries from decommissioned nodes (which is something we probably want to do eventually, but this does not represent a regression from the pre-CASSANDRA-705 status quo).

> refactor blocking io to use thread (and queue) per conn pool, not thread per socket
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-728
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-728
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: 728.txt
>
>
> this means the pool can be in charge of reconnecting and no caller has to block for that part, as discussed in Jaakko's feedback to CASSANDRA-705

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.