I am running multiple pollers, and we just noticed that the discovery of new hosts is not doing what we would expect when trying to partition the workload. Instead of doing a third of the new hosts, it does a third of all the hosts, essentially doing a full discovery, which is causing some our PDU’s to get overloaded, since they are being hit by 3 parallel discoveries and also possibly a poll at the same time.
/opt/observium/observium-wrapper discovery --host new -i 3 -n 0
If I remove the -i and -n options, then it does what I would expect, although it is not distributed, which isn’t a problem because the number of new devices should be pretty small. So the --host and the -i and -n options appear to be mutually exclusive, which isn’t stated in the help at all.
Hi Milton,
We generally recommend that you only run the "--host new" job on a single system in a distributed installation.
This is similar to housekeeping and other tasks that don't really distribute sanely.
I'll see if we can improve the logic.
Thanks, adam.
Milton Ngan via observium wrote on 18/04/2025 05:55:
I am running multiple pollers, and we just noticed that the discovery of new hosts is not doing what we would expect when trying to partition the workload. Instead of doing a third of the new hosts, it does a third of all the hosts, essentially doing a full discovery, which is causing some our PDU’s to get overloaded, since they are being hit by 3 parallel discoveries and also possibly a poll at the same time.
/opt/observium/observium-wrapper discovery --host new -i 3 -n 0
If I remove the -i and -n options, then it does what I would expect, although it is not distributed, which isn’t a problem because the number of new devices should be pretty small. So the --host and the -i and -n options appear to be mutually exclusive, which isn’t stated in the help at all.
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
participants (2)
-
Adam Armstrong -
Milton Ngan