Understand and prepare to use Cloudera Lakehouse Optimizer
Before you use Cloudera Lakehouse Optimizer , you must understand how a policy
works, the policy resources, and the prerequisites you must complete before you create a
policy.
How Cloudera Lakehouse Optimizer performs table maintenance Cloudera Lakehouse Optimizer and its components perform several operations in the background after you create or define a policy to initiate, evaluate, and complete the Iceberg table maintenance.What are Cloudera Lakehouse Optimizer policy resources Cloudera Lakehouse Optimizer policy consists of a JEXL script and JSON file, collectively referred to as policy resources. The JEXL script is mandatory, and the JSON file is optional. The default ClouderaAdaptive policy consists of the ClouderaAdaptive.jexl script and the ClouderaAdaptive.json file.High availability for Cloudera Lakehouse Optimizer Cloudera Lakehouse Optimizer ensures that the service is running when a Cloudera Lakehouse Optimizer instance fails during planned maintenance. In an HA deployment, you can run multiple Cloudera Lakehouse Optimizer service instances within the same cluster or Data Hub, and the system elects one leader instance to accept requests and modify shared state.State persistence for Cloudera Lakehouse Optimizer Cloudera Lakehouse Optimizer operational state such as scheduled tasks, triggers, and maintenance jobs handles service restarts, failures, and network issues. When you restart a Cloudera Lakehouse Optimizer instance, it resumes from persisted state in the shared database.Auditing for Cloudera Lakehouse Optimizer Cloudera Lakehouse Optimizer auditing provides an audit trail of user and system activities on the service, including policy changes, namespace operations, authentication events, and table maintenance actions. Audit events are written as NDJSON files to a configurable filesystem location. 