Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Minor docs fixes in 'Evaluate Druid' section.

This commit is contained in:
Jakub Kukul 2015-12-07 19:42:52 +01:00
parent b44fedb1cb
commit 8248f7f40c
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/content/misc/evaluate.md
View File

@ -40,7 +40,7 @@ It is recommended you follow the [example production configuration](../configura
The deep storage to use in this POC example can be S3 or HDFS.
1. node1: [Coordinator](../design/coordinator.html) + metadata store + zookeeper.
* node1: [Coordinator](../design/coordinator.html) + metadata store + zookeeper.
Example hardware: EC2 c3.2xlarge node (8 cores, Intel Xeon E5-2680 v2 @ 2.80GHz and 15GB of RAM).
See [here](../configuration/production-cluster.html) for the runtime.properties. Some example JVM configs for this hardware:
@ -54,15 +54,15 @@ See [here](../configuration/production-cluster.html) for the runtime.properties.
-XX:+UseConcMarkSweepGC
```
2. node2: [Broker](../design/broker.html)
* node2: [Broker](../design/broker.html)
Example hardware: EC2 c3.2xlarge node (8 cores, Intel Xeon E5-2680 v2 @ 2.80GHz and 15GB of RAM).
[Example configs](https://github.com/druid-io/druid-benchmark/tree/master/config) (see broker-* files).
2. node3: [Historical](../design/historical.html).
* node3: [Historical](../design/historical.html).
Example hardware: EC2 m3.2xlarge instances (8 cores, Intel Xeon E5-2670 v2 @ 2.50GHz with 160GB SSD and 30GB of RAM)
[Example configs](https://github.com/druid-io/druid-benchmark/tree/master/config) (see compute-* files).
3. node4 (optional): [Real-time](../design/realtime.html) node or [Overlord](../design/indexing-service.html) (depending on how you choose to ingest data).
* node4 (optional): [Real-time](../design/realtime.html) node or [Overlord (Indexing Service)](../design/indexing-service.html) (depending on how you choose to ingest data).
Example hardware: EC2 c3.2xlarge node (8 cores, Intel Xeon E5-2680 v2 @ 2.80GHz and 15GB of RAM).
For the real-time node, see [here](../configuration/production-cluster.html) for the runtime.properties. Use with the following JVM configs:
@ -76,7 +76,8 @@ For the real-time node, see [here](../configuration/production-cluster.html) for
-XX:+UseConcMarkSweepGC
```
For the overlord running in local mode to do all ingestion, see [here](../configuration/production-cluster.html) for the runtime.properties. Use with the following JVM configs:
For small ingest workloads, you can run the overlord in local mode to load your data.
To do so, see [here](../configuration/simple-cluster.md#overlord-node-indexing-service) for the runtime.properties. Use with the following JVM configs:
```
-server
@ -95,5 +96,3 @@ druid.indexer.runner.javaOpts="-server -Xmx6g -Xms6g -XX:NewSize=256m -XX:MaxNew
The coordination pieces (coordinator, metadata store, ZK) can be colocated on the same node. These processes do not require many resources, even for reasonably large clusters.
You can add more historical nodes if your data doesn't fit on a single machine.
For small ingest workloads, you can run the overlord in local mode to load your data.