cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-14002) Don't use SHA256 when building merkle trees
Date Wed, 08 Nov 2017 08:31:00 GMT


Marcus Eriksson updated CASSANDRA-14002:
    Status: Patch Available  (was: Open)

Patch for this [here|] -
it replaces the SHA-256 with Murmur3.

Murmur3 is only 128 bit though, so the patch instead hashes every value twice using 2 different
murmur3 instances with different seeds to get the same number of bits as SHA-256. The approach
used is similar to what guava does in its ConcatenatedHashFunction.

In my tests with semi-wide partitions (~100KB mean partition size) this reduces the time spent
building merkle trees with at least 50%.

cc [~mkjellman]

> Don't use SHA256 when building merkle trees
> -------------------------------------------
>                 Key: CASSANDRA-14002
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 4.x
> We should avoid using SHA-2 when building merkle trees as we don't need a cryptographic
hash function for this.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message