[jira] [Commented] (CASSANDRA-3772) Evaluate Murmur3-based partitioner

["Lex Lythius (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695804#comment-13695804 ] 

Lex Lythius commented on CASSANDRA-3772:
----------------------------------------

Sorry to bring a skeleton back with bad news from the day after it was buried.

Apparently, finding collisions for Murmur3 hash would be easy enough to attempt choking Cassandra.
http://emboss.github.io/blog/2012/12/14/breaking-murmur-hash-flooding-dos-reloaded/

Just wanted to make sure you are aware of this.
                
> Evaluate Murmur3-based partitioner
> ----------------------------------
>
>                 Key: CASSANDRA-3772
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3772
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>             Fix For: 1.2.0 beta 1
>
>         Attachments: 0001-CASSANDRA-3772.patch, 0001-CASSANDRA-3772-Test.patch, CASSANDRA-3772-v2.patch, CASSANDRA-3772-v3.patch, CASSANDRA-3772-v4.patch, hashed_partitioner_3.diff, hashed_partitioner.diff, MumPartitionerTest.docx, try_murmur3_2.diff, try_murmur3.diff
>
>
> MD5 is a relatively heavyweight hash to use when we don't need cryptographic qualities, just a good output distribution.  Let's see how much overhead we can save by using Murmur3 instead.

--
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: http://www.atlassian.com/software/jira