How Hub Startup Policy Affects Startup Behavior

Every hub must have one primary instance running to maintain communication with remote sites. The other instances are secondaries that act as backups to the primary.

You can specify which hub instances should start as primary and which as secondary in your distributed system. When a hub is initialized, it attempts to assume the role specified, but will start up even if it must assume a different role.

This table describes startup behavior for the three policies.

Gateway Hub Startup Policy and Startup Behavior

Startup Policy	Startup Behavior
none (default)	If no primary is running for the id, the hub starts as primary. Otherwise it starts as secondary.
primary	Same behavior as for none with the addition that the hub logs a warn­ing if it starts as secondary.
secondary	If a primary is present, the hub starts as secondary. If there is no pri­mary, the hub waits for up to one minute for a primary to start. If no primary starts in that time, the hub starts as primary and logs a warning.