Pausing and resuming table maintenance

You can pause or suspend the maintenance of a table, when required. For example, when there are a lot of writes or bulk ingestion. Cloudera Lakehouse Optimizer also pauses the table maintenance when certain criteria are met. You can resume the table maintenance when required.

The following steps show how to pause or resume table maintenance, how to list the policies in the paused list, and how to retrieve the reason for placing a table or namespace in the paused list.
  • Pause table maintenance using one of the following methods:
    • Go to the Cloudera Management Console > Lakehouse Optimizer UI > Tables tab, click for a table, and then click Pause Table.
    • Use one of the following REST APIs:
      • The PUT /tables/{tableId}/paused API pauses the maintenance of an Iceberg table.
      • The PUT /namespaces/{namespace}/paused API pauses the maintenance of Iceberg tables in the specified namespace.

    When you or Cloudera Lakehouse Optimizer places a table or namespace in the paused list, Cloudera Lakehouse Optimizer ignores the tables and namespaces in the paused list during the evaluation phase.

  • Resume table maintenance using one of the following methods:
    • Go to the Cloudera Management Console > Lakehouse Optimizer UI > Tables tab, click for a table, and then click Unpause Table.
    • Resume table maintenance by using one of the listed REST APIs:
      • Removes a table from the paused list using the DELETE /tables/{tableId}/paused API.
      • Removes the tables in the specified namespace from the paused list using the DELETE /namespaces/{namespace}/paused API.
      • Removes all the policies from the paused list using the DELETE /policies/paused API.
      • Removes the specified policy from the paused list using the DELETE /policies/{policyVersion}/paused API.
      • Removes all the tables from the paused list using the DELETE /tables/paused API.

    When you remove the table, policy, or namespace from the paused list, the evaluation phase resumes for the table maintenance depending on the CRON schedule set in the policy.

  • List the policies in the paused list using the GET /policies/paused API.
  • Retrieve the reason for pausing the policy by using one of the following APIs:
    • The GET /policies/{policyVersion}/paused API gets the reason for the specified paused policy.
    • The GET /tables/{tableId}/paused API gets the reason for the specified paused table.