Section | Description |
①Filter and search area | Filter instances to be submitted by entering the instance object name or ID. This method is useful for filtering for the required instances when you know the instance object ID or name. Submitted By Me: Select this option to filter for data backfill tasks submitted by the current account. Select Project: Filter by the project where the node resides. You can select multiple projects for which the current logged-on user has O&M-Access Folder permissions.
Note After you filter by project, the list displays only the instances of the selected projects in the data backfill workflow. Filter: Click Filter to expand the filter area. To filter again, click Reset to clear all filter conditions and restore the default settings. The supported filter options include the following: Recurrence: Filter instances by scheduling cycle type. Supported types are Daily, Weekly, and Monthly. You can select multiple types. Submitted By: Filter instances by submitter. Scheduled Running Time: Filter instances by their scheduled runtime. You can filter for instances scheduled for Today, Today and later, or a specific time period. Status: Filter instances by status. Supported statuses are Instance To Be Submitted, Instance Generation Failed, Paused, Submitting, and Instance Generated Successfully. Instance To Be Submitted: The instance will be generated and submitted to run the data backfill at a future time.
Note For auto triggered data backfill tasks, an instance to be submitted is generated at 23:00 on the day before the scheduled runtime. Instance Generation Failed: The data backfill instance cannot be generated due to a system failure or other reasons. For a failed instance, you can retry the operation. For more information, see Retry instances to be submitted. Paused: After an instance is paused, no runnable data backfill instances are generated. This does not affect already generated data backfill instances. To resume the instance, perform the resume operation. For more information, see Resume instances to be submitted. Submitting: The instance to be submitted is being submitted to generate a runnable data backfill instance. Instance Generated Successfully: The instance to be submitted has generated a runnable data backfill instance. You can view the generated data backfill instance on the submitted instances page. For more information, see Manage submitted instances.
|
②List operations | |
③List of instances to be submitted | The Instances to be Submitted page lists the instances to be submitted that are initiated by auto triggered tasks. The list includes the data backfill instance name, data timestamp, scheduling cycle, scheduled runtime, instance status, submitter, project, data backfill task, and supported O&M operations. The supported operations are as follows: Save as Data Backfill Task: For an instance to be submitted that is generated by a one-time data backfill, click to save it as a data backfill task. For more information, see Create a data backfill task. Resume: Resume instances that have a status of Paused.
Note When you resume a paused instance to be submitted, the system checks whether the scheduled runtime of the instance has been reached. If it has, the system automatically generates a data backfill instance and runs the data backfill operation. Pause: Pause instances that have a status of Instance to Be Submitted. After an instance is paused, no runnable data backfill instances are generated. This does not affect already generated data backfill instances. To resume a paused instance, click the icon in its Actions column. Retry: To retry an instance that has a status of Instance Generation Failed, click the icon in its Actions column.
|
④Batch operation area | Use the features in the batch operation area to process instances to be submitted in batches and improve operational efficiency. |