t; more clear.
>
> Again, thank you.
> On Wednesday, March 9, 2022 at 11:58:11 PM UTC+1 Dormando wrote:
> Hey,
>
> Unfortuantely I don't think it works that way. Warm restart is useful
> for
> upgrading or slightly changing the configuration of an indepe
.
On Wednesday, March 9, 2022 at 11:58:11 PM UTC+1 Dormando wrote:
> Hey,
>
> Unfortuantely I don't think it works that way. Warm restart is useful for
> upgrading or slightly changing the configuration of an independent cache
> node without losing the data.
>
> However s
Hey,
Unfortuantely I don't think it works that way. Warm restart is useful for
upgrading or slightly changing the configuration of an independent cache
node without losing the data.
However since you're expanding and contracting a cluster, keys get
remapped inbetween hosts. If you're saving
Hi all,
recently discovered about the Warm restart feature... simply awesome!
we use memcached as a look-aside cache and we run it in kubernetes, also
have autoscaling based on cpu... so when the number of requests increase
enough, a new memcached node is started... we can tolerate a temporary
ocess id
> > of Memcached
> >
> > but SIGUSR1 is a Unix/Linux signal for inter process communication and it
> > is not used in Windows.
> >
> > This is why my testing does not work in Windows.
> >
> > On Tuesday, 7 December 2021 at 11:35:00 U
efully it needs
>
> kill -SIGUSR1 where is the process id
> of Memcached
>
> but SIGUSR1 is a Unix/Linux signal for inter process communication and it is
> not used in Windows.
>
> This is why my testing does not work in Windows.
>
> On Tuesday, 7 December 2021
2021 at 11:35:00 UTC Damian Chapman wrote:
>
>> Hi all,
>>
>> I am trying to test Memcached warm restart on Windows.
>> I am using v1.6.12.
>>
>> I used ImDisk to create a RAM disk on Windows on the D: drive (1G)
>>
>> I start Memcached with the -e opt
why my testing does not work in Windows.
>
>> On Tuesday, 7 December 2021 at 11:35:00 UTC Damian Chapman wrote:
>> Hi all,
>>
>> I am trying to test Memcached warm restart on Windows.
>> I am using v1.6.12.
>>
>> I used ImDisk to create a RAM disk on Wind
in Windows.
On Tuesday, 7 December 2021 at 11:35:00 UTC Damian Chapman wrote:
> Hi all,
>
> I am trying to test Memcached warm restart on Windows.
> I am using v1.6.12.
>
> I used ImDisk to create a RAM disk on Windows on the D: drive (1G)
>
> I start Memcached with the -e opti
Hi all,
I am trying to test Memcached warm restart on Windows.
I am using v1.6.12.
I used ImDisk to create a RAM disk on Windows on the D: drive (1G)
I start Memcached with the -e option
C:\Users\chapmand\memcached\1.6.12\libevent-2.1\x64>memcached.exe -e
D:\backup
[restart] no metadata s
I got it to work! With your great help it wasn't that bad, or maybe I'm a
better sysadmin than I'm giving myself credit for. ;)
There were two steps, really. After creating the fstab line, I typed sudo
systemctl edit memcached.service. I entered this and saved:
[Service]
KillSignal=SIGUSR1
Absolutely. That's exactly the workflow it's designed for, we just haven't
updated any of the systemd scripts to be more friendly for it.
Also a caveat; there _was_ a bug fixed relatively recently with the
restart code. I don't know if ubuntu backports these. If you use large
objects (> 512k)
That's extremely helpful, thank you so much for this! I will look into it and
test on my staging server. I don't think systemd has ever killed or restarted
the process apart from once before I upgraded the RAM, so I'm not too worried
about the daily usage. But even systemd supports custom kill
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 standar
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
weird... I suspect that's something in your environment. It's certainly
not that way anywhere I've ever run it. I'm using it right now with a
space :)
On Mon, 9 Dec 2019, David Karlsen wrote:
> -e /cache_state/memory_file <-- fails-e/cache_state/memory_file <-- OK
>
> man. 9. des. 2019 kl. 22:58
-e /cache_state/memory_file <-- fails
-e/cache_state/memory_file <-- OK
man. 9. des. 2019 kl. 22:58 skrev dormando :
> example?
>
> On Mon, 9 Dec 2019, David Karlsen wrote:
>
> > OK, found it, apparently -e needs to be followed by path w/o any
> whitespace
> >
> > man. 9. des. 2019 kl. 21:54
example?
On Mon, 9 Dec 2019, David Karlsen wrote:
> OK, found it, apparently -e needs to be followed by path w/o any whitespace
>
> man. 9. des. 2019 kl. 21:54 skrev dormando :
> I'm not sure offhand. From my perspective I'd triple check what the
> path/file it's trying to open is
OK, found it, apparently -e needs to be followed by path w/o any whitespace
man. 9. des. 2019 kl. 21:54 skrev dormando :
> I'm not sure offhand. From my perspective I'd triple check what the
> path/file it's trying to open is (add a printf or something), else you're
> in container/kube territory
No. It is there and writable
man. 9. des. 2019 kl. 21:32 skrev dormando :
> Is the directory missing?
>
> On Mon, 9 Dec 2019, David Karlsen wrote:
>
> > OK, I hacked it together apt-installing some shared libs.With the patch
> applied I get:
> >
> > k logs test-memcached-0
> > failed to open
Noe
man. 9. des. 2019 kl. 21:32 skrev dormando :
> Is the directory missing?
>
> On Mon, 9 Dec 2019, David Karlsen wrote:
>
> > OK, I hacked it together apt-installing some shared libs.With the patch
> applied I get:
> >
> > k logs test-memcached-0
> > failed to open file for mmap: No such file
Is the directory missing?
On Mon, 9 Dec 2019, David Karlsen wrote:
> OK, I hacked it together apt-installing some shared libs.With the patch
> applied I get:
>
> k logs test-memcached-0
> failed to open file for mmap: No such file or directory
>
> Which is a bit strange - should not the file be
OK, I hacked it together apt-installing some shared libs.
With the patch applied I get:
k logs test-memcached-0
failed to open file for mmap: No such file or directory
Which is a bit strange - should not the file be created dynamically if it
does not exist?
fredag 6. desember 2019 23.51.38
OK, so I compiled with that changed (doing the same steps as in the
.travis.yml) - but it seems to use shared-libraries. Is there anyway to
compile this statically?
I also created a PR with the same change:
https://github.com/memcached/memcached/pull/587
lørdag 30. november 2019 18.03.23 UTC+1
It's going to use some caps (opening files, mmap'ing them, shared memory,
etc). I don't know what maps to which specific thing.
That error looks like an omission on my part..
mmap_fd = open(file, O_RDWR|O_CREAT, S_IRWXU);
if (ftruncate(mmap_fd, limit) != 0) {
perror("ftruncate
Does memcached use any of these capabilities:
https://unofficial-kubernetes.readthedocs.io/en/latest/concepts/policy/container-capabilities/
?
fre. 6. des. 2019 kl. 16:39 skrev David Karlsen :
> So far I am stuck on:
>
> k logs test-memcached-0
> ftruncate failed: Bad file descriptor
>
>
> -
So far I am stuck on:
k logs test-memcached-0
ftruncate failed: Bad file descriptor
- memcached
- -m 768m
- -I 1m
- -v
- -e /cache-state/memory_file
-vvv does not reveal anything interesting.
What could be the cause of this?
lørdag 30. november 2019 18.03.23 UTC+1 skrev
Sure will
Follow https://github.com/bitnami/charts/issues/1685
ons. 4. des. 2019, 08:20 skrev dormando :
> If you succeed you should share with the class :)
>
> On Sun, 1 Dec 2019, David Karlsen wrote:
>
> > Thank you - that explains it well. I'll look around if I can create a
> "durable"
If you succeed you should share with the class :)
On Sun, 1 Dec 2019, David Karlsen wrote:
> Thank you - that explains it well. I'll look around if I can create a
> "durable" tmpfs in k8s via a storageclass :)
>
> søn. 1. des. 2019 kl. 04:25 skrev dormando :
> The disk file is memory
Thank you - that explains it well. I'll look around if I can create a
"durable" tmpfs in k8s via a storageclass :)
søn. 1. des. 2019 kl. 04:25 skrev dormando :
> The disk file is memory mapped; that is the actual memory, now external to
> memcached. There's no flush at shutdown, it just
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
&g
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
36 matches
Mail list logo
