You can run the Tracker initial load job any time after the site is upgraded to TeamForge 17.1. We recommend that you run it before you hand over the site to the users. This task might take few hours depending on the amount of artifact data in the site.
You can run the job when the site is in use. On an average, there is 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 outage is remote immediately.
$ [RUNTIME_DIR]/scripts/etl-client.py -r TrackerInitialJob
./etl-client.py -a
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
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.
Yes, it is mandatory to run the initial load job for a new site.
You can run this any time after the site is upgraded to TeamForge 17.1. However, the Tracker incremental data harvesting is blocked until the initial load is run. This is true for an existing site that is upgraded to TeamForge 17.1 as well as for a new site.
The incremental load is made to fail if the initial load is not run. You can ignore this.