Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Auto-Pilot Monitoring enhances the provisioning ability of Lakehouse Optimizer in order to continually monitor on jobs and clusters that undergo a configuration change or are shared-compute

What Auto-Pilot does:

1. Automatic Provisioning

At each LHO restart and every 1h schedule, the Auto Pilot does the following when

  • if Global Init Script ENABLED

    • enables monitoring on all workloads that contain at least one task with Shared Access Mode cluster

    • all other jobs and clusters maintain their monitor status based on global init script option

  • if Global Init Script DISABLED

    • enables monitoring on all workloads by enabling Cluster-Scoped Init Scripts and individual cluster Spark configurations, using Secret Scopes

Auto-Pilot also allows admin users to enable monitoring on All-Purpose-Clusters that are owned by other users.

Ownership change is executed when Auto-Pilot is triggered at restart or on a schedule basis. In this scenario, the new temporary owner is set to the Service Principal used by LHO.

2. Automatic Telemetry Agent Update

When a new version of LHO is available, on upgrade the Auto Pilot will update the LHO Telemetry Agent in each published workspace.

Please see section Automatic Provisioning for more details.

How to enable/disable Auto-Pilot

  • env variables

    • AUTO_PILOT_ENABLED = true/false

    • default: true

Unity Catalog Support

If you are using Unity Catalog, Auto-Pilot requires additional configuration.

Please follow the following steps:

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.