Table of Contents | ||
---|---|---|
|
There are 5 jobs in sync service:
...
Table of Contents | ||
---|---|---|
|
Sequence Diagram for sync jobs:
...
01:29 PersonElasticSearchSyncJob
01:45 PostFundingStatusSyncJob
02:00 PersonRecordStatusJob
If the container is restarted in a pre-defined time range (00:00:00+00:00 to 07:00:00+00:00) then the jobs are run sequentially.
Job Execution Order
Summary of what to run:
...
PersonPlacementEmployingBodyTrustJob
...
Re-run PersonPlacementTrainingBodyTrustJob
and PersonElasticSearchSyncJob
...
Run jobs out of schedule
Instructions taken from Refresh Elasticsearch cache page.Note: All the time are here in UTC
Run jobs out of schedule
Where possible; it is easiest to use the web interface at the root of the application (https://<host IP/domain name here>/sync/.).
DEPRECATED:
If a job needs to be run manually, e.g. after a database has been re-imported to stagefrom the server, the instructions taken from Refresh Elasticsearch cache page can be used:
- Copy the commands below into your favorite text editor.
- Replace the
$bean_name
and$job_method
with the ones for the job you are re-running. - ssh into either the blue or green server and paste the modified commands in a single chunk and it will go through the process of:
- downloading the JDK and the JMX client
- copy them to the container
- extract the compressed JDK
- launch the JMX client and
- restart the sync job.
...