memsup, cpu_sup and disksup processes not available in the RabbitMQ 4.1.4

[Vishnu Vardhan]

Hi team,

I am using RabbitMQ version 4.1.4 and I am seeing that few supervisor processes that are part of previous releases are not available anymore at the time of application boot.

My understanding is they are still critical processes that monitor different resource consumption by the application and one of it directly linked to vm_memory_high_watermark.

So wanted to understand whether they are removed explicitly in this version of RabbitMQ or just disabled by default and can be started based on configuration changes.

I could not find any information about these processes being disabled/removed in the release notes so please clarify on this.

Thanks in advance.

[Luke Bakken]

Hello,

At this time, RabbitMQ does not use the resource monitor functions provided by Erlang/OTP and instead uses its own internal monitoring.. The fact that those processes were running in the past was un-intentional.

Thanks,

Luke