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

Persistence at Restart #370

Open
nunoperalta opened this Issue Mar 31, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@nunoperalta

nunoperalta commented Mar 31, 2018

Hello,

I really love Memcached, and that's what I've always used so far for all my projects.

However, as my projects have been growing, a restart (e.g. upgrading Memcached, restarting the server, etc...) is always an inconvenience, only because Memcached won't persist the data.

It's not so bad for cached data that can be retrieved from the database, but I store sessions in Memcached, and flush every few minutes to the database, to increase performance (and decrease database load).

However, when Memcached restarts, it causes an inconsistency in the sessions.
There are a few other things that are only stored in Memcached, that will be lost too.

Just wondering - is there any way I can make Memcached persist at restarts?

If not, are there plans to implement this in the future?
Or, is there a good reason for this not to be implemented? e.g. would that greatly decrease the performance of Memcached?

I see that Redis implements persistence, and a lot of people seem to be preferring Redis over Memcached.
However, in my case, I'm 99% happy with Memcached, and would be 100% if Persistence was available.

Thank you.

@dormando

This comment has been minimized.

Show comment
Hide comment
@dormando

dormando Mar 31, 2018

Member

#342 seen this by chance?

In general "cache is a cache" is a good argument, but I recognize this use case.. been clearing bugs and the DDoS fallout but I'll probably get this finished in the next month, maybe?

There're a lot of caveats with it: If you're going to miss invalidations while it's down, you now have cache inconsistency.. if you want to reboot, you'll need to copy the file to disk and back inbetween reboots, etc... but it should all work. The POC worked it's just not complete.

Member

dormando commented Mar 31, 2018

#342 seen this by chance?

In general "cache is a cache" is a good argument, but I recognize this use case.. been clearing bugs and the DDoS fallout but I'll probably get this finished in the next month, maybe?

There're a lot of caveats with it: If you're going to miss invalidations while it's down, you now have cache inconsistency.. if you want to reboot, you'll need to copy the file to disk and back inbetween reboots, etc... but it should all work. The POC worked it's just not complete.

@nunoperalta

This comment has been minimized.

Show comment
Hide comment
@nunoperalta

nunoperalta Mar 31, 2018

wow! That seems to be a lot of work done so far!

Very well done. Thank you very much for doing this.

No problem how long it might take - I'm glad that you're working on it.

Very kind regards.

nunoperalta commented Mar 31, 2018

wow! That seems to be a lot of work done so far!

Very well done. Thank you very much for doing this.

No problem how long it might take - I'm glad that you're working on it.

Very kind regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment