A supervisor scheduler contains a central configuration directory (in general named remote) for interchanging configuration files with one or more workload schedulers. Once a workload scheduler is started, it retrieves the configuration files from the supervisor's remote directory with an internal scheduler command sended via TCP.
Whenever a configuration file is changed in the remote directory of the supervisor, it sends a signal via UDP to all workload schedulers to inform them, that the configuration has changed.
Sometimes the signaling of the workload schedulers does not work, because the UDP port (or UDP in general) is blocked in the firewall of the workload scheduler. Currently you can't find any advise for this behavior in the scheduler log.
In the next release (1.3.9) you will see a WARN in the scheduler log, if it's not possible to place the signal 'configuration is changed' via UDP to a remote scheduler:
*SCHEDULER-474 Workload scheduler is not responding to UDP message since 2010-09-09 14:28:50.000 UTC (72s). Workload scheduler's configuration can not be updated.]