[
https://issues.apache.org/jira/browse/CASSANDRA-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788135#action_12788135
]
Jonathan Ellis commented on CASSANDRA-617:
------------------------------------------
Wouldn't it be worth making gossip state names an enum? This would (a) make it
harder to screw things up with name collisions, and (b) make name part of
gossip load almost negligible.
Avinash also suggested:
* Compress the messages which are being sent. I have seen 5:1 compression is
achievable. So if you send 117 per the JIRA this is automatically 500+.
* If and if absolutely necessary move to TCP and compress and send all
digests. Then all the problems go away.
IMO [jbellis again] if we can get to ~500 with compression and the simpler
fixes (your Syn fix, move state optimization, enum names) then that gives us a
long time before any current user of Cassandra needs to worry about the
complexity of adding multiple messages per round (or the even bigger change of
moving to TCP).
> gossiper scalability
> --------------------
>
> Key: CASSANDRA-617
> URL: https://issues.apache.org/jira/browse/CASSANDRA-617
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.5
> Reporter: Jaakko Laine
> Fix For: 0.5
>
> Attachments: averages.png, spread_100.png, spread_50.png,
> spread_90.png
>
>
> Improve gossiper scalability.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
