Summary: This section decribes the mechanism of replicating client notify registrations.

Replicate Notify Template and Trigger Notify Template Options

The replication group includes the ability to replicate notification registration, and the ability to trigger events that are a result of replication and not direct client operation to the source space.

Here are the system behaviors when using these options:

Replicate Notify Template Setting Trigger Notify Template Setting Explanation
True False Client gets notification from the primary space while it is active after registration.
If failover has been configured, it gets notification from the replica space when the primary space fails.
False True Client gets notification only from those spaces that it registered for notification.
Notification occurs when data has been delivered to the space, either by a client application or from the replication.
True True Client gets notification from all cluster spaces after registration.
Client gets multiple notifications for every space event.
False False Client gets notification only from those spaces to which it registered.
Client does not get notifications from spaces which received their data by replication.

Replicate notify templates and trigger notify templates are orthogonal. However, if you enable them both, you should be aware that for each space object that matches the notify template and is replicated to another space, you get an event. This may result in more events than you initially intended. You can use the source of the event to check which space triggered it.

Notify Recovery

When the cluster-config.notify-recovery property is true, it tries to recover the notify template from one of the replication group members. If it does not succeed, it then tries to recover notify templates from the other cluster members.

GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence