Who provides enterprise support for Apache Druid?
The Apache Druid project sells no support; Imply and other firms on the community page do. AceMQ covers Druid you operate, with response from 15 minutes by plan, 24/7. A Sev 1 such as halted ingestion means an engineer on a bridge reading supervisor status.
Why is Druid streaming ingestion behind?
The supervisor shows whether tasks are failing and restarting, running out of slots, or rejecting rows. Check ingest/kafka/lag, task logs and ingest/events/unparseable before adding tasks.
Why are our Druid queries slowing down?
Usually segment count: many small segments mean more per-segment work for the Brokers and Historicals. Compaction and segment granularity are the fix, followed by processing thread and merge buffer sizing.
How big should Druid segments be?
Check the shape with sys.segments. We aim for segments sized to your query patterns and rows per segment, then compact to that; the right numbers depend on your data.
Why did enabling rollup make storage bigger?
Rollup only merges rows with identical dimension values. A high-cardinality dimension such as a request ID stops it merging anything.
How do we upgrade Druid safely?
Follow the documented service order, drain streaming tasks first, rehearse on a copy of your specs, and keep a rollback plan for the metadata store.
Do you support Druid with Kafka and Kinesis?
Yes. We tune supervisors, check offset handling and task slot supply, and set expectations about exactly-once delivery. When lag appears, we read task logs and unparseable counts before recommending more tasks.
What does a Druid health check include?
We review ingestion lag and rejection rates, segment size and count, compaction, tier capacity, query latency, metadata store and deep storage permissions. You get a written list ranked by production risk, with the query behind each item.
Can we pay for a Druid health check without signing for a year?
Yes. A health check, a compaction plan or an upgrade rehearsal can each be a stand-alone project with a fixed deliverable. If you want 24/7 cover and engineers who remember your specs and tiers, the annual plan builds on that work.
What should we expect to pay for Druid support?
Most annual contracts sit between $24,000 and $72,000 (USD). Inputs include the number of data servers and query servers, streaming supervisors from Kafka or Kinesis, storage tiers, whether Imply is in the mix, and the response target. Describe the cluster and we quote within 1 hour.