In VM-based environments, deleting the profiler
cluster (or in Compute Cluster enabled environments deleting the profiler jobs) removes
all the Custom Sensitivity Profiler rules and other updates to the specific cluster. It
could also cause loss of data specific to currently applied rules on the deleted
profiler cluster.
To overcome this situation, when you decide to delete the profiler cluster or (in VM-based environments) the
profiler jobs by Compute Cluster enabled
environments, there is a provision to retain the status of the Custom
Sensitivity Profiler rules:
If your profiler cluster or profiler jobs
have rules that are not changed or updated, you can directly delete them or the profiler cluster.
If the rules were modified or updated, you have an option to download the
modified rules along with deletion. The modified rules consist of the suspended
system rules and the deployed custom rules. Using the downloaded rules, you can
manually add or modify them to your newly added profiler jobs or the profiler cluster.
On the Search page, select the data lake from the drop-down.
Click Delete Profiler.
If you agree, select the warning message I understand this action
cannot be undone.
Click Delete.
The application displays the following message.
Additionally, note that you can delete the profiler cluster in these
situations, when:
Profiler cluster is up and running
Profiler cluster is created but stopped
Profiler cluster creation failed but is registered with the data
lake