Update from murmur2 to murmur3 hash.
Bug #738235 reported by
Bob Vincent
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libmemcached |
Fix Released
|
Low
|
Brian Aker |
Bug Description
Updated libhashkit/murmur.c from murmur2 to murmur3.
Related branches
lp:~tangent-org/libmemcached/1.0-build
- Tangent Trunk: Pending requested
-
Diff: 287 lines (+48/-50)10 files modifiedexample/include.am (+1/-1)
libmemcached/common.h (+8/-1)
libmemcached/connect.cc (+3/-10)
libmemcached/connect.hpp (+0/-2)
libmemcached/get.cc (+2/-2)
libmemcached/instance.cc (+0/-5)
libmemcached/stats.cc (+2/-2)
libmemcached/string.cc (+13/-8)
libmemcached/version.cc (+15/-15)
libtest/comparison.hpp (+4/-4)
Changed in libmemcached: | |
milestone: | none → 1.0.15 |
importance: | Undecided → Low |
status: | Incomplete → In Progress |
Changed in libmemcached: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I get a crash after applying your code:
Testing set==27877== Invalid write of size 4 generate_ hash_with_ redistribution (hash.c:115)
==27877== at 0x4C1C6FC: hashkit_murmur (murmur.c:91)
==27877== by 0x4C142ED: memcached_
Wouldn't we want to have a murmur version 2 and 3 so that anyone who is using it today won't end up with data on different nodes?