[didip]

We found the opposite. Setting up Druid clusters is the easiest compared to its competitors: Clickhouse and Pinot.

Especially since ingestion goes straight to S3. We don’t really worry about backups (just deal with PG backups).

Just make sure your ZK is happy and all will be well.

The hard part about Druid is tuning:

- the ingestions: Spec definition, compaction, sharding strategy, RAM consumptions, etc.

- and query performance: RAM consumptions, number of threads, timeouts, etc.

[doliveira]

How is the documentation for this deployment and tuning? Last time I checked I had the impression that anything about the dozen of different node types weren't very clear, not to mention details about the ingestion were all over the place.

And it was hard to find examples of configuration, ingestion other than basic tutorials

[didip]

Docs definitely have rooms for improvement.

Architecturally, It is easier to visualize this two big group:

- query serving: coordinator, historical, broker

- ingestion: overlord, middlemanager

router unifies all of Druid API together.

I would start with the Helm chart to get some basic idea on tunings.

[hobofan]

> Just make sure your ZK is happy and all will be well.

That sounds like the opposite of easy to setup (and maintain).

[dominotw]

We had druid in production and this was our main weak link. Its really hire to find people who know how to operate ZK well in production.