KBI 311228 Issue Addressed: Daughter Engine Services Might Miss Monitoring Tasks Due To Frequent Recycling When Non-Stop Motors Are Used

Version

Argent Advanced Technology 3.1A-1504-A or earlier

Date

Wednesday, 3 June 2015

Summary

Argent AT Daughter Engine may recycle frequently and miss monitoring tasks when the Mother Engine implements Argent Non-Stop Motors

The remote Daughter Engine downloads the latest Master Control Information from a Mother Non-Stop Motor; any one of the pool of Mother Non-Stop Motors is selected at random

In order to push out latest control information to Daughter Engines, customer can either export the Master Control Information manually on Supervising Engine screen, or rely on auto export to allow Argent AT service exporting automatically

However, it might not be desirable to enable auto export, especially during the initial system configuration phase

Service may push out Rule, Relators that customer has not fully tested

When customer exports the Master Control Information from a Mother Non-Stop Motor, the export file resides on the Motor where exporting is done

It can take up to 5 minutes for other Motors to synchronize the exported file

But before the Master Control Information is synchronized, other Mother Non-Stop Motors still have the older version of export file

When Daughter Engine checks for new control information, it randomly connects to one of the Motors

Depending on which Mother Non-Stop Motor the Remote Daughter Engine connects to, the Remote Daughter Engine may download either old or new version of Master Control Information

When the Remote Daughter Engine downloads Master Control Information different from the one downloaded and imported previously, the Remote Daughter Engine recycles to import

Before Mother Non-Stop Motors have fully synchronized the export file, it is possible that Daughter Engine downloads the old version, then new version, then old version again etc

As a result, Daughter Engine can recycle repeatedly

Monitoring tasks are not performed while Daughter Engine is recycling

By default, Daughter Engine communicates with Mother Engine once every 5 seconds

The recycling can happen quite frequently and Monitoring Tasks can be missed significantly

The issue has been addressed in Argent AT 3.1A-1504-T1

The Master Control Information export program has been enhanced to copy to other Mother Non-Stop Motor after having successfully exported locally

In case of offline Mother Non-Stop Motor, the built-in synchronization mechanism can still guarantee the latest Master Control Information is copied when the Motor is back online

Technical Background

N/A

Resolution

Upgrade to Argent AT 3.1A-1504-T1 or later