cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michał Michalski (JIRA) <>
Subject [jira] [Commented] (CASSANDRA-3378) Allow configuration of storage protocol socket buffer
Date Mon, 19 Nov 2012 10:16:59 GMT


Michał Michalski commented on CASSANDRA-3378:

I started to investigate this task (lfh label sounds like a good point to get deeper into
Cassandra architecture ;-) ), but as I'm new to Cassandra internal architecture, I'm not really
sure if I understand the subject of this task. To be more precise - I have a problem with
understanding what does "storage protocol" really refers to in this case?

At first I thought it refers to Thrift (and ThriftServer started by CassandraDaemon), but
when I was investigating this issue (by checking how "looking at rpc_[send,recv]_buff_size_in_bytes"
setting is set and where) I discovered that ThriftServer already uses the setting mentioned
in this task. 

My second idea was "native server" (org.apache.cassandra.transport.Server) which I found in
CassandraDaemon too. It uses ServerBootstrap created using NioServerSocketChannelFactory and
it seems possible to add such setting there, but I wonder if this is really the service this
issue tells about? Or maybe I'm completely wrong? Could you give me some clue? 

Sorry if it's a silly question, but I'm confused ;-)

BTW: Is there maybe a doc that tells a bit more on how Cassandra works in terms of "internal"
architecture/dependencies/protocols etc.?
> Allow configuration of storage protocol socket buffer
> -----------------------------------------------------
>                 Key: CASSANDRA-3378
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Brandon Williams
>            Priority: Minor
>              Labels: lhf
> Similar to rpc_[send,recv]_buff_size_in_bytes, we should expose this for high latency

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message