Resizing post-requisites

Complete the following tasks after you resize a Data Lake.

If RAZ is not being used, resync the IDBroker mappings to the Data Lake.
Reapply your custom Cloudera Manager configurations.
Start the Cloudera Data Warehouse Database Catalogs and Virtual Warehouses. For each virtual warehouse, Cloudera recommends that you start, stop, and start again. This will completely refresh the Data Lake details for the virtual warehouse.

warning
You must be aware of an issue where the Database Catalog goes into an error state after a Data Lake resize. For more information about this known issue, see the Cloudera Data Warehouse 1.9.3-b166 (released December 5, 2024) release notes.
Start the Cloudera Data Hub cluster services if you stopped them before the resizing operation. Data Hubs that were stopped before the resizing operation should continue to work when the resizing completes, by communicating with the new Data Lake automatically when they are re-started.
Resize up the FreeIPA cluster. See Resize FreeIPA.
With Cloudera DataFlow 2.1 or higher, the steps below are sufficient. For older Cloudera DataFlow versions, you must re-create the impacted flows.
1. An alert suggesting restart of the flow is triggered in the Cloudera DataFlow service.
2. Restart the Flows.
3. After restart, the flows should start working with the resized Data Lake. Not all Cloudera Flows will be impacted by a resized Data Lake. Only those Flows that have a dependency on the Data Lake will be alerted.
Resume the Cloudera AI workbenches.