Comment 2 for bug 1534519

This condition could be hit in following conditions:
1) Increased limit for kernel.pid_max - some value greater than ~1 million
2) Big amount of nodes in cluster - but it will require at least 32 nodes with default linux pid_max value

Proper fix will be included in rabbitmq 3.6.1 ( https://github.com/rabbitmq/rabbitmq-server/pull/552 ). It could be backported to any version of rabbitmq starting from 3.5.0.

For earlier versions (as for 3.3.5 in the initial report) we'll need to add some shell magic instead - if it is deemed to be important enough.