Gerhard Lazu

And then it was restarted by the Varnish daemon.

Right.

So Fly is aware that there is a process on the machine that is using too much memory and more memory is being requested.

And then it looks like, okay, which process do I kill?

And in this case, a process with the most memory will get shot and will get killed.

So the Fly platform, it integrates with that functionality, which is a kernel, it's a Linux functionality, right?

That's why like an out of memory crash would happen.

Even like if you have a single machine, you have too much memory, you don't have any swap.

How do you basically give more memory when there's no memory left and when the system is becoming unstable?

So then you get like just a single process which gets killed.

In Fly's case, they surface that.

They surface the fact that there was like an out of memory crash.

There was an out of memory event.

And they send you an email when that happens.

It doesn't mean that the machine had to restart.

It doesn't mean that he stopped serving traffic.

It just means there was like something that just had to go away because it was using too much memory.

And I say too much memory.

Obviously, it's a bit more complicated than that because something was asking for memory.

The kernel didn't have any more memory to allocate.