The disk file is memory mapped; that is the actual memory, now external to
memcached. There's no flush at shutdown, it just gracefully stops all
in-flight actions and then does a fast data fixup on restart.
So it does continually read/write to that file. As I said earlier you can
create an
Won’t the cache be written to file at shutdown and not contionously while
running?
søn. 1. des. 2019 kl. 03:58 skrev dormando :
> Hey,
>
> It's only guaranteed to work in a ram disk. It will "work" on anything
> else, but you'll lose deterministic performance. Worst case it'll burn out
>
Hey,
It's only guaranteed to work in a ram disk. It will "work" on anything
else, but you'll lose deterministic performance. Worst case it'll burn out
whatever device is underlying because it's not optimized for anything but
RAM.
So, two options for this situation:
1) I'd hope there's some way
https://github.com/memcached/memcached/blob/master/restart.c#L283
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to memcached+unsubscr...@googlegroups.com.
To
it's a file system, tem point about warm restart is reset server and load
previous data, and how to do this? kill the proess with the proper signal
Em sáb., 30 de nov. de 2019 às 15:03, David Karlsen
escreveu:
> Reading https://github.com/memcached/memcached/wiki/WarmRestart it is a
> bit
Reading https://github.com/memcached/memcached/wiki/WarmRestart it is a bit
unclear to me if the mount *has* to be tmpfs backed, or it can be a normal
fileystem like xfs.
We are looking into running memcached through Kubernetes/containers - and
as a tmpfs volume would be wiped on pod-recreation
