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
Enhancement: Extstore + WarmRestart #871
Comments
Hey, No real workaround, sorry. It's on the roadmap for soon, blocked by getting the proxy released. I can't exactly speak to when other than sooner than later :( It's not incredibly difficult to do but is probably more than a day of work. |
@dormando Thanks! Not sure how the process works I will be happy to contribute with some testing once released, just let me know, otherwise thanks again. |
Hi @dormando, I really think it would be very beneficial, I also got an additional candidate project I could apply it too :-) Thanks a mill! |
It's quite a slog, but getting there. I always accept more sponsors to help with time/motivation :) |
You are more than welcome and thanks for your time and contribution! 👍 |
mark |
Hi,
I tried implementing the Extstore feature (https://github.com/memcached/memcached/wiki/Extstore) combined with the WarmRestart (https://github.com/memcached/memcached/wiki/WarmRestart) but I get the following message after a graceful restart:
memcached[5869]: [restart] memory restart with extstore not presently supported.
Otherwise the 2 features work fine independently.
I guess it is not (yet) possibile to combine them together?
I'm not an expert here but I feel like it would be good to have it working... at present I'm loosing a lot of large cached objects from the Extstore on restart.
FYI, I tried with MemCacheD 1.6.14 on CentOS 7.
I appreciate any advice or a workaround for this scenario.
Thanks!
The text was updated successfully, but these errors were encountered: