chaosblade icon indicating copy to clipboard operation
chaosblade copied to clipboard

blade create mem load --mode ram is unstable

Open anxvi opened this issue 2 years ago • 5 comments

We use chaosblade for chaos engineering in a big company, version 1.4.0, and that's what we discovered:

Although we specify the low rate (1-16 MB/s) on high loads (above 80% RAM), the blade immediately reaches the 99% load and the process is killed. The flag --avoid-being-killed keeps it alive just 2-3 seconds more.

What we are aiming to achieve is having a stable high load at 95 and 100%. We guess that the rates are somehow being ignored.

Have you ever come up with this issue before? How can we fix this? The status is fine but ps aux shows the proccess terminates very quickly.

anxvi avatar Jul 01 '22 13:07 anxvi

Please provide the linux system and kernel version. The avoid-being-killed parameter works on some systems, some doesn't

xcaspar avatar Jul 08 '22 06:07 xcaspar

Please provide the linux system and kernel version. The avoid-being-killed parameter works on some systems, some doesn't

OS is RHEL Server 7.9 and Kernel version is Linux 3.10.0-1160.42.2.e17.x86_64

anxvi avatar Jul 08 '22 09:07 anxvi

Please provide the linux system and kernel version. The avoid-being-killed parameter works on some systems, some doesn't

By the way, we checked through ps aux, the parameter actually escalates the priority of the process so it lasts a little longer than usually but still gets killed

anxvi avatar Jul 11 '22 08:07 anxvi

Then it's gone?

imooni avatar Sep 07 '22 07:09 imooni

Then it's gone?

No, it's not

anxvi avatar Sep 07 '22 11:09 anxvi