Can I ask what the purpose of the sequential, blocking ping processes spawned by the Monitor are? They’re bringing it to a standstill when looking at our remote farm.
Seems I spoke too soon about them blocking… the Monitor had frozen. However, I’m still curious what their purpose is.
I think thats when the monitor updates the ‘ping’ column of the slaves…
I REALLY wish we could turn that off, its generating a lot of broadcast traffic, as we have machines that are offline due to physical moves etc.
Hmm, I hadn’t even noticed that column… is that a legacy feature from the D5 days?
Yeah, this was mostly a carry-over feature from D5. It was meant as a way to tell if the Slave machines were running/reachable or not, but it honestly doesn’t make a ton of sense on bigger farms.
This is being turned off by default in D7.
It’s useful on small farms to see if a slave is Offline or Off.
Btw, this came up internally, that the best would be if that ping column would be populated by the pulse machine and the data would be in the db. Because it is sometimes useful information, but 1-200 monitors flooding the network is probably bad… If pulse just handled that it would be much less traffic, and it could ping only offline/disabled/stalled machines periodically
As long as there’s an option to disable it completely, I’m fine with any idea.