. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 41.8. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication 'primary' ha policy we can explicitly set the 'coordination-id' to a common value for all peers in a cluster. For multi primary: so it may not be immediately recognisable or human-readable, however it will ensure that all 'peers' coordinate. 36.2.4. Shared Store When using a shared store both primary and backup servers share

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 40.8. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication 'primary' ha policy we can explicitly set the 'coordination-id' to a common value for all peers in a cluster. For multi primary: so it may not be immediately recognisable or human-readable, however it will ensure that all 'peers' coordinate. 35.1.4. Shared Store When using a shared store, both live and backup servers share

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 40.8. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication 'primary' ha policy we can explicitly set the 'coordination-id' to a common value for all peers in a cluster. For multi primary: so it may not be immediately recognisable or human-readable, however it will ensure that all 'peers' coordinate. 35.1.4. Shared Store When using a shared store, both live and backup servers share

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 40.8. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication 'primary' ha policy we can explicitly set the 'coordination-id' to a common value for all peers in a cluster. For multi primary: so it may not be immediately recognisable or human-readable, however it will ensure that all 'peers' coordinate. 35.1.4. Shared Store When using a shared store, both live and backup servers share

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 41.7. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication primary ha-policy we can explicitly set the coordination-id to a common value for all peers in a cluster. peers" coordinate. 36.3. Failing Back to Primary Server After a primary server has failed and a backup

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 41.7. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication primary ha-policy we can explicitly set the coordination-id to a common value for all peers in a cluster. peers" coordinate. 36.3. Failing Back to Primary Server After a primary server has failed and a backup

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 41.7. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication primary ha-policy we can explicitly set the coordination-id to a common value for all peers in a cluster. peers" coordinate. 36.3. Failing Back to Primary Server After a primary server has failed and a backup

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 41.7. Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . replication primary ha-policy we can explicitly set the coordination-id to a common value for all peers in a cluster. peers" coordinate. 36.3. Failing Back to Primary Server After a primary server has failed and a backup

are transferred to another endpoint. Receivers The broker pulls messages from another endpoint. Peers The broker creates both senders and receivers on another endpoint that knows how to handle them. same destination. This creates an infinite loop of sends and receives. Broker Connections 74 Peers The broker can be configured as a peer which connects to the Apache Qpid Dispatch Router and instructs replication 'primary' ha policy we can explicitly set the 'coordination-id' to a common value for all peers in a cluster. For multi primary : Note: the string value provided will be converted internally

are transferred to another endpoint. Receivers The broker pulls messages from another endpoint. Peers The broker creates both senders and receivers on another endpoint that knows how to handle them same destination. This creates an infinite loop of sends and receives. Broker Connections 87 Peers The broker can be configured as a peer which connects to the Apache Qpid Dispatch Router and instructs replication 'primary' ha policy we can explicitly set the 'coordination-id' to a common value for all peers in a cluster. For multi primary : High Availability and Failover 398 Note: the string value provided