How to Delete an Executor Pool Using the OpenAPI Swagger UI – DataHub Customer Support Portal

Area: API Issues

Sub-Area: Remote Executor Pool Management

Issue

Users who have created remote executor pools and later need to remove them — for example, after renaming pools for better naming conventions or decommissioning old executors — may find there is no delete button available in the DataHub Cloud UI. This is a known product gap: the UI and GraphQL API only expose create, update, and list operations for remote executor pools. However, a self-service deletion path does exist via the OpenAPI Swagger UI, which exposes a delete endpoint for the datahubRemoteExecutorPool entity.

You Might Be Asking

How do I delete a remote executor pool in DataHub?
Is there a delete button for executor pools in the DataHub UI?
Can I remove a stopped executor pool that has no associated sources?
How do I clean up unused or old executor pools after renaming?

Solution

You can delete a remote executor pool using the OpenAPI Swagger UI. Follow the steps below:

Navigate to the OpenAPI Swagger UI for your DataHub instance:

https://<your-instance>.datahubproject.io/openapi/swagger-ui/index.html

Locate the executor pool section. In the Swagger UI, find and expand the section titled:
```
datahubRemoteExecutorPool Entity
```
Open the DELETE endpoint within that section and click Try it out.
Enter the URN of the executor pool you wish to delete. The URN follows this format:
```
urn:li:dataHubRemoteExecutorPool:<your-pool-name>
```
For example, if your pool is named my-ecs-executor, the URN would be:
```
urn:li:dataHubRemoteExecutorPool:my-ecs-executor
```
Execute the request by clicking Execute. Confirm that a successful (2xx) response is returned.
Verify the deletion by navigating to the Executors page in the DataHub UI and refreshing. The deleted pool should no longer appear.

Additional Notes

The DataHub Cloud UI and GraphQL API do not currently expose a delete operation for remote executor pools — only create, update (including description/rename), and list operations are supported through those interfaces. The OpenAPI Swagger UI endpoint described above is the supported self-service method for pool deletion. If you need to confirm the URN of a pool before deleting it, you can list existing pools via the same Swagger UI or by checking the Executors page in the DataHub UI. It is safe to delete a pool that is in a stopped state with no associated ingestion sources; however, always verify there are no active sources attached to a pool before deleting it. This behavior may change in a future release as a dedicated delete UI feature has been requested.

Issue

You Might Be Asking

Solution

Additional Notes

Related Documentation