DataHub · Rate Limits

Datahub Rate Limits

DataHub Core is self-hosted, so there are no vendor-imposed rate limits — throughput is bounded by the operator's GMS (Generalized Metadata Service) replicas, the underlying Kafka / Elasticsearch / SQL backends, and any reverse-proxy throttling the operator configures. DataHub Cloud (the managed Acryl/datahub.com service) does not publish numeric request-per-second limits on the public site; tenant capacity is sized to the contract.

Datahub Rate Limits is the machine-readable rate-limit profile for DataHub on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests_per_second.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Data Catalog, Metadata, Open Source, and Rate Limiting.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Data CatalogMetadataOpen SourceRate Limiting

Limits

DataHub Core operator-configured limit deployment
requests_per_second
operator-defined
Self-hosted; throughput is gated by GMS replica count, Kafka throughput, and Elasticsearch / SQL backend capacity. Use a reverse proxy (Nginx, Envoy) for external throttling.
DataHub Cloud tenant capacity tenant
requests_per_second
see datahub.com — sized to contract
DataHub Cloud capacity is provisioned per customer; numeric ceilings are not published.

Policies

Self-Hosted Throttling (Core)
For DataHub Core, scale GMS pods and use a reverse-proxy rate-limit module if needed. Backoff on 503 from the GMS.
Bulk Ingestion Pacing
Metadata ingestion via the Python emitter or CLI should batch events and pace throughput to avoid saturating the metadata change log topic.
GraphQL Query Cost
Prefer narrow GraphQL queries with field selection; deep lineage walks can spike backend load and induce 503s.
Cloud SLA
DataHub Cloud is SLA-backed at 99.5% availability; tenants should still implement retry with exponential backoff on transient errors.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/datahub-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.