You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2016/02/12 17:38:18 UTC

[jira] [Resolved] (CASSANDRA-9256) Refactor MessagingService to support pluggable transports

     [ https://issues.apache.org/jira/browse/CASSANDRA-9256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne resolved CASSANDRA-9256.
-----------------------------------------
    Resolution: Later

> Refactor MessagingService to support pluggable transports
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-9256
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9256
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benedict
>
> CASSANDRA-7029 and CASSANDRA-9237 would both benefit greatly from a pluggable MessagingService.
> Ideally, we would refactor the native transport to use the same abstractions, so that we could have a single implementation of each viable transport mechanism for both, and we can easily test out the impact of any transport on the whole cluster, not just one half. This is especially important for establishing if there is a benefit to approaches that permit us to isolate networking to a single thread/core, as the characteristics would be quite different if we still needed many networking threads for the other half of the equation.



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