Apache/druid
1
0
Fork 0
mirror of https://github.com/apache/druid.git synced 2025-02-13 21:45:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
druid/docs/operations/single-server.md
Gian Merlino d007477742
Docusaurus build framework + ingestion doc refresh. (#8311) 
* Docusaurus build framework + ingestion doc refresh.

* stick to npm instead of yarn

* fix typos

* restore some _bin

* Adjustments.

* detect and fix redirect anchors

* update anchor lint

* Web-console: remove specific column filters (#8343)

* add clear filter

* update tool kit

* remove usless check

* auto run

* add %

* Fix resource leak (#8337)

* Fix resource leak

* Patch comments

* Enable Spotbugs NP_NONNULL_RETURN_VIOLATION (#8234)

* Fixes from PR review.

* Fix more anchors.

* Preamble nix.

* Fix more anchors, headers

* clean up placeholder page

* add to website lint to travis config

* better broken link checking

* travis fix

* Fixed more broken links

* better redirects

* unfancy catch

* fix LGTM error

* link fixes

* fix md issues

* Addl fixes
2019-08-20 21:48:59 -07:00

2.7 KiB
Raw Blame History

id title
single-server Single server deployment

Druid includes a set of reference configurations and launch scripts for single-machine deployments:

  • micro-quickstart
  • small
  • medium
  • large
  • xlarge

The micro-quickstart is sized for small machines like laptops and is intended for quick evaluation use-cases.

The other configurations are intended for general use single-machine deployments. They are sized for hardware roughly based on Amazon's i3 series of EC2 instances.

The startup scripts for these example configurations run a single ZK instance along with the Druid services. You can choose to deploy ZK separately as well.

The example configurations run the Druid Coordinator and Overlord together in a single process using the optional configuration druid.coordinator.asOverlord.enabled=true, described in the Coordinator configuration documentation.

While example configurations are provided for very large single machines, at higher scales we recommend running Druid in a clustered deployment, for fault-tolerance and reduced resource contention.

Single Server Reference Configurations

Micro-Quickstart: 4 CPU, 16GB RAM

Launch command: bin/start-micro-quickstart Configuration directory: conf/druid/single-server/micro-quickstart

Small: 8 CPU, 64GB RAM (~i3.2xlarge)

Launch command: bin/start-small Configuration directory: conf/druid/single-server/small

Medium: 16 CPU, 128GB RAM (~i3.4xlarge)

Launch command: bin/start-medium Configuration directory: conf/druid/single-server/medium

Large: 32 CPU, 256GB RAM (~i3.8xlarge)

Launch command: bin/start-large Configuration directory: conf/druid/single-server/large

X-Large: 64 CPU, 512GB RAM (~i3.16xlarge)

Launch command: bin/start-xlarge Configuration directory: conf/druid/single-server/xlarge