java - how to fix "stale data access" in memcached -


we facing issue memcached (v1.4.4 on redhat) accurately described below:

with consistent ketama hashing in memcached, there no strict state given key lives. in absence of up-to-date key-server remapping info, clients might read or write key wrong memcached server , lead either stale or inconsistent data. example, if there network disruption, , 1 or more clients decide particular memcached server not available anymore, automatically rehash data rest of nodes if original 1 still available. if node returns service (for example after network outage resolved), data on node out of date , clients without updated keyserver remapping info read stale data.

is there way solve without going expensive commercial software alternative?

if still have troubles implementation, gave input similar question here: how handle recovery memcached nodes when using spymemcached & hashalgorithm.ketama_hash too.


Comments

Popular posts from this blog

linux - Does gcc have any options to add version info in ELF binary file? -

android - send complex objects as post php java -

charts - What graph/dashboard product is facebook using in Dashboard: PUE & WUE -