The "Synchronize"/"Element Synchronize" scheduled jobs should only be enabled on the Distributed eHealth Console (Reporting Front End)
Enabling these jobs on the Distributed eHealth Systems (Back-end Pollers) as well will cause performance issues in the cluster.
CA eHealth does not immediately replicate information for elements and group members (elements assigned to groups) when you add, modify, or delete them. Since elements and group members are known only to the CA eHealth system on which they are created and the Distributed eHealth Consoles—these objects are not considered global objects.
After you discover new elements, modify or delete elements, or change group memberships, and you save the changes locally (on the Distributed eHealth System that you are using), CA eHealth does not replicate the changes to the Distributed eHealth Consoles in the cluster. Instead, Distributed eHealth Consoles use the scheduled Synchronize job and Element Synchronize job to obtain these changes during the day.
By default, the Synchronize job runs at 11 p.m. each day to gather these changes from the Distributed eHealth Systems in the cluster. When the job runs, each Distributed eHealth Console sends a request to the other CA eHealth systems in the cluster to obtain the latest object information that they have. Each CA eHealth system responds with its information. You can change the time when the Synchronize job runs to select a low-activity time on the CA eHealth system.
By default, the Element Synchronize job runs first at 3:30 a.m. each day, and then every four hours thereafter, to gather new, modified, and deleted element information and changes in group membership information from the other CA eHealth systems in the cluster. When the job runs, each Distributed eHealth Console sends a request to the Distributed eHealth Systems in the cluster to obtain the element and group membership changes that have occurred since the last Element Synchronization. Each CA eHealth system responds with its information.