Set the number of update-notifier threads

The policy server is responsible for synchronizing all database replicas in the domain.

When a change is made to the master database, notification threads announce this change to all replicas configured to receive update notifications. Each replica must then download the new information or the changes from the master.

The policy server configuration file, ivmgrd.conf, contains a stanza entry for setting the maximum number of update-notifier threads. This pool of threads allows simultaneous (parallel) notification.

For example, to concurrently notify 30 replicas of a database change, the thread pool must be set to at least 30. If there are more than 30 replicas, another round of notifications occurs (in this example, 30 at a time). All replicas are guaranteed to be notified, regardless of the value of this stanza entry.

The performance goal of the update-notifier threads value is to announce a database change as quickly as possible. Generally the value must be set to equal the number of existing replicas. This results in the performance advantage of a single pool of threads quickly accomplishing the notification task to all replicas at once. The default event notifier thread pool is set as:

[ivmgrd]
max-notifier-threads = 10

When the auto-database-update-notify stanza entry is set to yes, we must correctly configure this stanza entry and also the notifier-wait-time stanza entry. See also Set the notification delay time.

Parent topic: Policy server administration tasks