Hi,
Satellites are what you think, but they don't really lower the load, because the Master still needs to do the 'backend' part of the polling, only the pollers are distributed.
All data is stored in the master. So, it still have around the same load.
This is useful in situations where the master can't access the remote network directly, or when you want 2 pollers polling the same host in case some of them die.
I expect that in the future the satellite system will case lighter loads.
Another option is implementing some patches sent to me by Anders
Karlsson that make the RRD Storage and Graphing distributed too, so the
master will ask the childs (slaves) for graphs, but the polling is local
to the slave.
Javier
Thanks a lot for the info. It's very interesting because of the high amount of hosts and interfaces
that are polled. With the stable version of JFFNMS I can use a seperate machine for polling and another
for the backend processing. I guess it would take some load of the backendmachine, althoug I can't estimate if
it's worth the effort. Can you?
Does using a dual cpu machine make any sense for JFFNMS?
I'm not very fond of using an unstable version of JFFNMS. Are those patches, made by Anders Karlsson, going to be merged with a stable version of JFFNMS in the (near) future?
Tjerk Nan
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ jffnms-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jffnms-users
