[
https://issues.apache.org/jira/browse/CASSANDRA-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-4383:
----------------------------------------
Attachment: 0001-Add-HOST_ID-and-TOKENS-app-states-binary-serialization.txt
Patch to promote hostId and tokens to their own app states. I decided to
suppress tokens in the gossipinfo output, and likewise left hostIds as strings,
since the savings from encoding those in binary is not much and maintaining a
list of things we do need to convert back to a human readable format will get
tedious. Having a huge list of tokens in gossipinfo is actually a bit
counterproductive for troubleshooting gossip issues anyway, and the information
is available elsewhere.
What's left now is about a zillion tests to rewrite (again) to support the new
states.
> Binary encoding of vnode tokens
> -------------------------------
>
> Key: CASSANDRA-4383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4383
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 1.2.0
>
> Attachments:
> 0001-Add-HOST_ID-and-TOKENS-app-states-binary-serialization.txt, 4383-v1.txt
>
>
> Since after CASSANDRA-4317 we can know which version a remote node is using
> (that is, whether it is vnode-aware or not) this a good opportunity to change
> the token encoding to binary, since with a default of 256 tokens per node
> even a fixed-length 16 byte encoding per token provides a great deal of
> savings in gossip traffic over a text representation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
