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 2 Next »

Configure Cluster Scope Init Script Storage

cluster-init-script - is a LHO script that copies the LHO Telemetry Agent jar from DBFS to the storage area accessible by clusters, i.e. /Volumes

Unity Catalog Enabled

Shared-Compute resources are available only with Unity Catalog enabled.

At the moment of this documentation creation, Databricks does not offer an API to upload the cluster-init-script in /Volumes.

Step 1) Use the following link to download the LHO

cluster-init-script

  • https://bplmdemoappstg.blob.core.windows.net/libraries/LHO_VERSION/init_script.sh

    • e.g. https://bplmdemoappstg.blob.core.windows.net/libraries/2.7.2/init_script.sh

Step 2) Upload script downloaded before to

/Volumes/main/default/bp-lakehouse-monitor/script/

The complete path should look like:

/Volumes/main/default/bp-lakehouse-monitor/script/init_script.sh

Step 3) In Databricks

  • open Catalog

  • open Metastore details

  • open Allowed JARs/Init Scripts

  • add a new entry for

/Volumes/main/default/bp-lakehouse-monitor/script/init_script.sh

Unity Catalog Disabled

This configuration step is done automatically by LHO when LHO Telemetry Agent is updated.

LHO copies the cluster-init-script into the storage area accessible by the cluster, i.e. the Databricks workspace files

/Workspace/bp-lakehouse-monitor/script/init_script.sh

  • 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.