Tech Tip:  What is synchronization and replication in eHealth Cluster  would do?

Document created by Yulun.Zhang Employee on Sep 11, 2014Last modified by SamCreek on Dec 17, 2016
Version 2Show Document
  • View in full screen mode

Synchronization in ehealth cluster - Synchronization process pulls objects from other cluster members to a machine where Synchronization command is issued. Element synchronization and general synchronization are the two scheduled synchronization jobs by default run from RFE, 

 

Element synchronization run every four hours for collecting new, modified, or deleted element information and group membership information from the backend pollers in the cluster into RFE.

 

Below is how the job command and log file look like:

 

$NH_HOME/bin/sys/nhiSynchronize -cluster -objType element,groupSection -checkContext

 

Cluster Sync initiated:

            Synchronizing objects of type element ... OK

            Synchronizing objects of type groupSection ... OK

 

Scheduled Job ended at '02/08/2009 19:30:25'.

 

General synchronization job is scheduled to run on RFE each night to update the RFE with the latest element, group membership, and any other new or modified object information such as group and group list from backend pollers. Below is how the job command log file looks like:

 

$NH_HOME/bin/sys/nhiSynchronize -cluster -checkContext

 

Cluster Sync initiated:

            Synchronizing objects of type element ... OK

            Synchronizing objects of type group ... OK

            Synchronizing objects of type groupSection ... OK

            Synchronizing objects of type groupList ... OK

            Synchronizing objects of type groupListContents ... OK

            Synchronizing objects of type serviceProfile ... OK

 

Scheduled Job ended at '02/07/2009 23:00:49'.

 

 

Replication in ehealth cluster – replication process pushes objects from a machine where the objects are created to other cluster members. Groups, group lists, group list members, and service profiles are global objects because their information is shared with all eHealth systems in the cluster. When you save the changes to one of these objects, eHealth automatically and immediately replicates the information for these objects to the other eHealth systems in the cluster. For example, you create a group named Boston_routers on poller1 and add three routers into the group as group members, and then you verify the group is added and three members are existed in the group in poller1. Since Replication happens automatically and immediately, Boston_routers group is added to the rest of the cluster members. But it will be empty on all machines except for poller1 it was created on. The group members are NOT updated on other cluster members. Now you can run nhSynchronize –cluster -allElements from RFE to update the element information from the poller1 for the group and verify that the group and its members of three elements exist on RFE.

Attachments

    Outcomes