How is the load determined and what masters are used by pmloadcheck.
The Privilege Manager client gathers and maintains statistics (load and response time information) for each of configured masters. The information is updated at regular polling intervals (60 minutes by default) by the pmloadcheck daemon and also whenever the client sends a request to a specific master. The statistics are reset every day at midnight by pmloadcheck.
The client makes load balancing decisions based on this information. The masters themselves do not have any direct control over how load balancing decisions are made on the clients.
The order in which pmloadcheck lists the available masters is the order that the client would use if command had been issued at that precise moment. However, even the pmloadcheck connections are taken into account when calculating load, so if masters are equally loaded, the next pmrun could very likely choose a different master than the pmloadcheck showed at the top of the list. This order changes as the pmloadcheck updates it’s information on the masters. Furthermore, the client will randomly select between equally loaded servers if "selcthostrandom yes" is set.
The pmloadcheck –f command will display the information gathered for each master, the –h flag can also be used to specify a single master on which to report.
Some explanations of the -f output:
“Master Load” shows the number of sessions that the master has since midnight.
“Local Load to master” shows the number of connections (including pmloadcheck updates) the client has made to the master.
“Last Checked At:” shows the time the client last connected to this server with either pmrun or pmloadcheck.