New versions of DataForge are continuously released and patched as the platform evolves and new features are added. To easily stay up to date with the latest versions, enable the maintenance settings in your environment. View the instructions below to modify maintenance schedules and enable or disable these features. Please submit a support ticket to the DataForge support team if assistance is needed.
Checking status of maintenance needed
A bell icon will display in the top-left corner of the UI next to the main menu if there is a mainenance version available, maintenance is in progress, or maintenance failed to complete. Click the bell icon to view more details. In the event of an upgrade failure (orange bell color), please reach out to DataForge Support to troubleshoot what went wrong.
Users can also manually check for new maintenance versions by navigating to the Service Configuration page and selecting the "Check for Upgrade" option on the triple-dot menu.
How does the maintenance process work?
When Maintenance starts, DataForge disables new ingestions and waits one hour for currently running processes to complete. If processes are still running at the 1-hour mark, maintenance deployment will fail processes and capture the failed process IDs in a metadata deploy.upgrade table. Once all processes are stopped, the maintenance deployment will proceed. Upon maintenance completion, failed processes are automatically queued for retry.
NOTE: Major version deployments as well as maintenance requiring infrastructure changes will be performed during the same Maintenance window.
Adjusting the maintenance schedule
Every environment will have a schedule named "Maintenance [System]". The default schedule is set to run on Wednesdays at 3pm UTC.
Users can edit this schedule by adjusting the cron values and saving the changes. However, it needs to be set to a workday weekday, with a time between 2PM and 8PM UTC. Ideally, set this schedule to a window when there aren't any scheduled processes to run.
Changes to this schedule will only take affect after Core is restarted, or the next time the previous schedule had it set to run. For directions on Restarting Core to finish this process, revisit Restarting Core from the Service Configurations page.
Here is an example of the default schedule that runs every Wednesday at 3pm UTC.
Example maintenance schedule starting Wednesdays at 3pm UTC
Enabling maintenance
To enable this feature, login to the DataForge environment and open the Main Menu. Select the System Configuration menu option and further select the Service Configurations page.
Navigating to the Service Configurations
Find the "auto-upgrade-enabled" row in the service configuration table and select the pencil icon in the Action column to edit. Click the toggle to switch it to enabled or On. Save the changes using the "Save" button in the top right.
Enable auto-upgrade-enabled toggle and Save
After saving the change, a message appears to the user that Core needs to be restarted for the change to take effect.
Notice to Restart Core
Users will also need to restart Core after making changes to the upgrade schedule.
Restarting core from the service configurations page
On the Service Configurations page, users can restart the Core service by selecting the triple-dot menu in the top right and selecting the "Restart Core" option.
Restart Core service from Service Configurations
Disabling maintenance
Follow the same steps as in Enabling Maintenance to edit the setting in the Service Configurations except clicking the toggle this time disables the process. Core needs to be restarted again as a last step for the feature to be turned off. DataForge highly discourages disabling the maintenance activities as only the latest versions of the product are supported.
Updated