Skip to content

support writing to multiple upstream servers ( sharding ) #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
helmus opened this issue Dec 7, 2017 · 0 comments
Open

support writing to multiple upstream servers ( sharding ) #31

helmus opened this issue Dec 7, 2017 · 0 comments

Comments

@helmus
Copy link

helmus commented Dec 7, 2017

It would be pretty awesome if memc could write to all upstreams on a cache miss, or support some function that will decide on a specific server based on crc of the key, this is how django works trough the python-memcached library example: python-memcached/memcache.py#L70

Right now a user will get as much caches misses as there are servers which is unfortunate.

An additional reason to support this is that memc currently will write to multiple upstream servers individually, but will not revoke the stale results on subsequent upstream writes, which may them result in stale cache hits, effectively making it impossible to use this lib with multiple upstream servers if stale hits are not acceptable.

somewhat related to #30 as this is a different solution ( maybe better ) for the same issue.

@helmus helmus changed the title support writing to multiple upstreams support writing to multiple upstream servers Dec 8, 2017
@helmus helmus changed the title support writing to multiple upstream servers support writing to multiple upstream servers ( sharding ) Dec 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant