Fredhopper uses a regular time frame every Monday between 11:00 UTC and 14:00 UTC to apply changes to the managed services infrastructure. These changes typically involve extensions to the infrastructure itself, but also the addition of new services and environments and reconfiguration of existing environments.
In this time frame access to the services below might be limited:
- Data transformations (ETL) may not be started.
- Active triggers may be cancelled and report FAILURE as status.
- Uploaded triggers might stay in UNKNOWN status for the duration of the maintenance window.
- Upload/download to Fredhopper Services API may not work.
During the maintenance window:
- The query service remains up and running at full capacity.
- The business manager remains available (unless it was already stopped because of a reindex trigger).
After the maintenance window is completed, service is resumed and any pending triggers are picked up and processed.
If your trigger reported FAILURE as status you have to resubmit it in order to make sure it will be processed.
Note that it might happen that your trigger reports FAILURE as status but that still all data has been processed normally. The FAILURE status is actually OK as the triggered process has been cancelled.
|
|
If, after the maintenance window, you have a trigger that appears to be "hung" (displays a RUNNING status for several hours without any sign of progress), please open a ticket and we can manually abort it for you so you can try uploading it again. Oftentimes, the trigger will process normally on the second attempt with no configuration change needed.
Kommentare
0 Kommentare
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.