After you verify whether you can access Cloudera Lakehouse Optimizer REST
APIs, Cloudera recommends following the best practice of performing a health check of the
service, and then verifying whether the ClouderaAdaptive default policy is available in the
Cloudera Lakehouse Optimizer service.
-
Ensure that the Cloudera Lakehouse Optimizer service and its components
are available and healthy using the GET /config/health API.
curl --location 'https://[***LAKEHOUSE OPTIMIZER ENDPOINT***]/cdp-proxy-token/clo/api/v1/config/health' \ --header 'Authorization: Bearer [**JWT Token**]'
By default, Cloudera Lakehouse Optimizer performs a partial
health check. To perform a full health check, append scope.
curl --location 'https://[***LAKEHOUSE OPTIMIZER ENDPOINT***]/cdp-proxy-token/clo/api/v1/config/health?scope=full' \ --header 'Authorization: Bearer ey'
When high availability (HA) is enabled, the
full health check response also includes a High
Availability entry that reports the HA status of the instance.
The entry indicates whether the instance is the leader or a standby, and
whether leader election is in progress. For more information, see High
availability for Cloudera Lakehouse Optimizer.
-
Verify whether the
ClouderaAdaptive default policy is
available in the Cloudera Lakehouse Optimizer service using the
GET /policies/resource API. The API fetches the default
ClouderaAdaptive policy details.
curl --location 'https://[***LAKEHOUSE OPTIMIZER ENDPOINT***]/api/v1/policies/resource?uri=clo%3A%2F%2Ftps%3Adefault%2FClouderaAdaptive' \ --header 'Authorization: Bearer ey'