You can run the initial load job any time after the site is upgraded to TeamForge
16.10. We recommend that you run
it before you hand over the site to the users.
You can run the job when the site is in use. On an average, there might be a ten percent
degradation in the response time when the job is running. If the job is not run as a
part of the upgrade, we recommend that you run it at a time when the site usage is
relatively low. The initial load job may consume more time to complete and this depends
on the data available in the site. So this job should be triggered when the site is
stable after the upgrade and the chances of site shut down is remote.
Note: The initial
load job can be run immediately in case of a fresh installation.
How do I list all the ETL jobs?
You can list all the ETL jobs by running the following command.
How do I run the initial load jobs?
Run the scripts specified below to run the initial load jobs.
- $ [RUNTIME_DIR]/scripts/etl-client.py -r
SCMCommitInitialJob
- $ [RUNTIME_DIR]/scripts/etl-client.py -r
TrackerInitialJob
What happens if I run an initial load job that has already run
successfully?
Re-running the initial load job does no harm. The system performs an internal check
and the job is aborted.
How do I check the status of the job?
Site administrators will be notified through mails if there is a job failure. The
following command will help you identify whether a job is currently running or not.
- $ [RUNTIME_DIR]/scripts/etl-client.py -a
What happens if there is a job failure?
An email will be sent to site administrators in case of a failure. The job should be
re-triggered manually. Data will be harvested from the last completed milestone
prior to the failure.
Is it mandatory to run the initial load job for a new site?
Yes, it is mandatory to run the initial load job for a new site.
What happens if I miss running the initial load during the installation or
upgrade?
You can run this any time after the site is upgraded to TeamForge
16.10. However, the
incremental data harvesting is blocked until the initial load is run. This is true
for an existing site that is upgraded to TeamForge
16.10 as well as for a
new site.
Why does the incremental_etl job fail when the initial load job is not
triggered?
The incremental load is made to fail if the initial load is not run. You can ignore
this.