You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rick Branson (JIRA)" <ji...@apache.org> on 2014/05/10 23:57:49 UTC
[jira] [Commented] (CASSANDRA-6815) Decided if we want to bring
back thrift HSHA in 2.0.7
[ https://issues.apache.org/jira/browse/CASSANDRA-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993814#comment-13993814 ]
Rick Branson commented on CASSANDRA-6815:
-----------------------------------------
FYI I reopened CASSANDRA-6285 because the "fix" doesn't fix the issue at all.
> Decided if we want to bring back thrift HSHA in 2.0.7
> -----------------------------------------------------
>
> Key: CASSANDRA-6815
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6815
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Pavel Yaskevich
>
> This is the followup of CASSANDRA-6285, to decide what we want to do regarding thrift servers moving forward. My reading of CASSANDRA-6285 suggests that the possible options includes:
> # bring back the old HSHA implementation from 1.2 as "hsha" and make the disruptor implementation be "disruptor_hsha".
> # use the new TThreadedSelectorServer from thrift as "hsha", making the disruptor implementation "disruptor_hsha" as above
> # just wait for Pavel to fix the disruptor implementation for off-heap buffers to switch back to that, keeping on-heap buffer until then.
> # keep on-heap buffer for the disruptor implementation and do nothing particular.
> I could be missing some options and we can probably do some mix of those. I don't have a particular opinion to offer on the matter.
--
This message was sent by Atlassian JIRA
(v6.2#6252)