Hey, I might have to look at how ubuntu's install works.. it might not be set up for this.
These are the basic steps for a restart: 1) set up memcached as you did, tmpfs/etc. 2) when you want to stop gracefully, issue a `kill -SIGUSR1 $(pidof memcached)` (kill is the command to send signals to a process) 3) start memcached again with the same options, and it will recover its data. This will _not_ survive reboots. This will survive software upgrades, which ubuntu isn't going to do anyway :) To survive reboots you need a few more steps: 1) once memcached has stopped, copy the files created in /tmpfs_mount_memcached/ to an actual harddrive somewhere. 2) reboot. 3) copy the datafiles back in place. 4) start memcached again. For this to be reliable you probably don't want ubuntu to automatically manage the process (disable auto start/restart in systemd). You might want to engage some community/chat/something for some systems admnistration help to get this going. Sounds like you're a bit over your head :( good luck, -Dormando On Wed, 10 Jun 2020, Even Onsager wrote: > My site runs on one webserver and we rely heavily on memcached to make it > snappy, to the extent that a reboot will make the site unresponsive for hours. > So imagine my joy when I saw the warm restart addition, and the fact that > Ubuntu Server 20.04 LTS has a new enough version in its repo. > > But the wiki left me scratching my head. This is what I have: > > - The standard apt package for Ubuntu 20.04 (version 1.5.22) > - `-e /tmpfs_mount_memcached/memory_file` in memcached.conf > - `-m 920` in memcached.conf > - `tmpfs /tmpfs_mount_memcached tmpfs nodev,nosuid,size=930M 0` in /etc/fstab > (generated by Ansible's mount module) > > No type of restart (neither of the systemd service nor the server itself) > seems to work. After restarting the size of the cache store is 0 and all pages > take forever to load. But is it supposed to work like this with tmpfs mounts? > I thought tmpfs wasn't meant to survive reboots? Am I misreading the wiki? > > I'm obviously in way over my head here (I don't even really know what a > SIGUSR1 is), so I'd really appreciate some help as to what I'm missing! > > And thanks for memcached - it's served my site well for years now, and after > upgrading to Rails 5 with better caching, we're using it more and more. :) > > -- > > --- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/memcached/afb47849-1915-4183-9765-457e7e4bc153o%40googlegroups.com. > > -- --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/memcached/alpine.DEB.2.21.2006101506060.27659%40dskull.
