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

Merge pull request #1334 from himanshug/fix_default_indexing_service_name 

fix doc for druid.[host,port,service] etc
This commit is contained in:
Xavier Léauté 2015-05-02 23:05:14 -07:00
parent f734471f22 fd3b23072b
commit 592ba565e0
7 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/content/Broker-Config.md
View File

@ -14,9 +14,9 @@ The broker node uses several of the global configs in [Configuration](Configurat
|Property|Description|Default|
|--------|-----------|-------|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|none|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|none|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|none|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|InetAddress.getLocalHost().getCanonicalHostName()|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|8082|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|druid/broker|
### Query Configs

2
docs/content/Configuration.md
View File

@ -246,7 +246,7 @@ This config is used to find the [Indexing Service](Indexing-Service.html) using
|Property|Description|Default|
|--------|-----------|-------|
|`druid.selectors.indexing.serviceName`|The druid.service name of the indexing service Overlord node. To start the Overlord with a different name, set it with this property. |overlord|
|`druid.selectors.indexing.serviceName`|The druid.service name of the indexing service Overlord node. To start the Overlord with a different name, set it with this property. |druid/overlord|
### Announcing Segments

6
docs/content/Coordinator-Config.md
View File

@ -14,9 +14,9 @@ The coordinator node uses several of the global configs in [Configuration](Confi
|Property|Description|Default|
|--------|-----------|-------|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|none|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|none|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|none|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|InetAddress.getLocalHost().getCanonicalHostName()|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|8081|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|druid/coordinator|
### Coordinator Operation

6
docs/content/Historical-Config.md
View File

@ -14,9 +14,9 @@ The historical node uses several of the global configs in [Configuration](Config
|Property|Description|Default|
|--------|-----------|-------|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|none|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|none|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|none|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|InetAddress.getLocalHost().getCanonicalHostName()|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|8083|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|druid/historical|
### General Configuration

6
docs/content/Indexing-Service-Config.md
View File

@ -13,9 +13,9 @@ The indexing service uses several of the global configs in [Configuration](Confi
|Property|Description|Default|
|--------|-----------|-------|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|none|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|none|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|none|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|InetAddress.getLocalHost().getCanonicalHostName()|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|8090|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|druid/overlord|
#### Task Logging

10
docs/content/Production-Cluster-Configuration.md
View File

@ -99,7 +99,7 @@ JVM Configuration:
Runtime.properties:
```
druid.host=#{IP_ADDR}:8080
druid.host=#{IP_ADDR}
druid.port=8080
druid.service=druid/prod/overlord
@ -155,7 +155,7 @@ JVM Configuration:
Runtime.properties:
```
druid.host=#{IP_ADDR}:8080
druid.host=#{IP_ADDR}
druid.port=8080
druid.service=druid/prod/middlemanager
@ -219,7 +219,7 @@ JVM Configuration:
Runtime.properties:
```
druid.host=#{IP_ADDR}:8080
druid.host=#{IP_ADDR}
druid.port=8080
druid.service=druid/prod/coordinator
```
@ -259,7 +259,7 @@ JVM Configuration:
Runtime.properties:
```
druid.host=#{IP_ADDR}:8080
druid.host=#{IP_ADDR}
druid.port=8080
druid.service=druid/prod/historical
@ -316,7 +316,7 @@ JVM Configuration:
Runtime.properties:
```
druid.host=#{IP_ADDR}:8080
druid.host=#{IP_ADDR}
druid.port=8080
druid.service=druid/prod/broker

6
docs/content/Realtime-Config.md
View File

@ -14,9 +14,9 @@ The realtime node uses several of the global configs in [Configuration](Configur
|Property|Description|Default|
|--------|-----------|-------|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|none|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|none|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|none|
|`druid.host`|The host for the current node. This is used to advertise the current processes location as reachable from another node and should generally be specified such that `http://${druid.host}/` could actually talk to this process|InetAddress.getLocalHost().getCanonicalHostName()|
|`druid.port`|This is the port to actually listen on; unless port mapping is used, this will be the same port as is on `druid.host`|8084|
|`druid.service`|The name of the service. This is used as a dimension when emitting metrics and alerts to differentiate between the various services|druid/realtime|
### Realtime Operation