Area: Product Issues
Sub-Area: Remote Executor Configuration
Issue
When managing Remote Executor Pools in DataHub Cloud, users may find that there is no option in the UI to delete an existing pool. This can be confusing for administrators who need to remove unused or misconfigured pools, as the deletion operation is not exposed through the standard product interface and must instead be performed via the DataHub API by a user with Admin privileges.
You Might Be Asking
- How do I delete a Remote Executor Pool in DataHub Cloud?
- Why is there no delete button for Remote Executor Pools in the UI?
- Can I remove a Remote Executor Pool without contacting support?
- What API endpoint do I use to delete a Remote Executor Pool?
Solution
To delete a Remote Executor Pool, you must use the DataHub GraphQL API directly. Follow the steps below:
- Ensure you have Admin access. Only users with the Admin role in DataHub Cloud can perform this operation. Verify your role in Settings → Users & Groups.
-
Retrieve the URN of the Remote Executor Pool you want to delete. You can find this in the DataHub UI under the Remote Executor Pool details, or by querying the API:
Note thequery listRemoteExecutorPools { listRemoteExecutorPools(input: { start: 0, count: 50 }) { total executorPools { urn id name } } }urnvalue for the pool you wish to remove. -
Execute the delete mutation via the GraphQL API. Navigate to your DataHub instance's GraphQL explorer at:
Then run the following mutation, substituting the URN retrieved in the previous step:https://<your-instance>.datahubproject.io/api/graphql
A successful response will returnmutation deleteRemoteExecutorPool { deleteRemoteExecutorPool(urn: "urn:li:dataHubExecutorPool:<your-pool-id>") }true. -
Verify deletion. Re-run the
listRemoteExecutorPoolsquery from Step 2 to confirm the pool no longer appears, or refresh the Remote Executor Pools section in the DataHub Cloud UI.
Additional Notes
- This limitation applies to DataHub Cloud (managed SaaS). UI-based deletion of Remote Executor Pools may be introduced in a future release.
- Deleting a pool that is actively assigned to ingestion sources may cause those sources to fail. Reassign or update any dependent ingestion sources before deleting the pool.
- The GraphQL explorer is accessible at
/api/graphqlon your DataHub Cloud instance and requires an authenticated session or a valid Personal Access Token (PAT) passed in theAuthorizationheader asBearer <your-pat>. - If you do not have Admin access, contact your DataHub Cloud account administrator to perform this operation on your behalf.
Related Documentation
- Setting Up a Remote Ingestion Executor
- DataHub GraphQL API Overview
- Personal Access Token Management
Tags: remote-executor, executor-pool, delete, api, graphql, datahub-cloud, ingestion, admin, managed-datahub, configuration