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

Docs on default ports.

This commit is contained in:
Gian Merlino 2016-03-14 11:25:21 -07:00
parent 61cd838d6b
commit e51277b96c
1 changed files with 22 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/content/tutorials/cluster.md
View File

@ -258,6 +258,25 @@ Keep -XX:MaxDirectMemory >= numThreads*sizeBytes, otherwise Druid will fail to s
Please see the Druid [configuration documentation](../configuration/index.html) for a full description of all
possible configuration options.
## Open ports (if using a firewall)
If you're using a firewall or some other system that only allows traffic on specific ports, allow
inbound connections on the following:
- 1527 (Derby on your Coordinator; not needed if you are using a separate metadata store like MySQL or PostgreSQL)
- 2181 (ZooKeeper; not needed if you are using a separate ZooKeeper cluster)
- 8081 (Coordinator)
- 8082 (Broker)
- 8083 (Historical)
- 8090 (Overlord)
- 8091, 8100–8199 (Druid Middle Manager)
- 8200 (Tranquility Server, if used)
<div class="note caution">
In production, we recommend deploying ZooKeeper and your metadata store on their own dedicated hardware,
rather than on the Coordinator server.
</div>
## Start Coordinator, Overlord, Zookeeper, and metadata store
Copy the Druid distribution and your edited configurations to your coordination
@ -311,10 +330,10 @@ This also allows you take advantage of Druid's built-in MiddleManager
autoscaling facility.
</div>
If you are doing push-based stream ingestion with Kafka or over HTTP, you can also start Tranquility server on the same
hardware that holds MiddleManagers and Historicals. For large scale production, MiddleManagers and Tranquility server
If you are doing push-based stream ingestion with Kafka or over HTTP, you can also start Tranquility Server on the same
hardware that holds MiddleManagers and Historicals. For large scale production, MiddleManagers and Tranquility Server
can still be co-located. If you are running Tranquility (not server) with a stream processor, you can co-locate
Tranquility with the stream processor and not require Tranquility server.
Tranquility with the stream processor and not require Tranquility Server.
```bash
curl -O http://static.druid.io/tranquility/releases/tranquility-distribution-0.7.2.tgz