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

minor documentation fixes in Tasks.md, index.md, indexing-service.md

This commit is contained in:
sahner 2015-06-19 17:09:53 -05:00
parent 0a5bb909a2
commit 4ba34fe43d
3 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/configuration/index.md
View File

@ -68,7 +68,7 @@ The indexing service also uses its own set of paths. These configs can be includ
If `druid.zk.paths.base` and `druid.zk.paths.indexer.base` are both set, and none of the other `druid.zk.paths.*` or `druid.zk.paths.indexer.*` values are set, then the other properties will be evaluated relative to their respective `base`.
For example, if `druid.zk.paths.base` is set to `/druid1` and `druid.zk.paths.indexer.base` is set to `/druid2` then `druid.zk.paths.announcementsPath` will default to `/druid1/announcements` while `druid.zk.paths.indexer.announcementsPath` will default to `/druid2/announcements`.
The following path is used service discovery and are **not** affected by `druid.zk.paths.base` and **must** be specified separately.
The following path is used for service discovery. It is **not** affected by `druid.zk.paths.base` and **must** be specified separately.
|Property|Description|Default|
|--------|-----------|-------|

4
docs/content/configuration/indexing-service.md
View File

@ -95,7 +95,7 @@ The overlord can dynamically change worker behavior.
The JSON object can be submitted to the overlord via a POST request at:
```
http://<COORDINATOR_IP>:<port>/druid/indexer/v1/worker
http://<OVERLORD_IP>:<port>/druid/indexer/v1/worker
```
Optional Header Parameters for auditing the config change can also be specified.
@ -153,7 +153,7 @@ Issuing a GET request at the same URL will return the current worker config spec
To view the audit history of worker config issue a GET request to the URL -
```
http://<COORDINATOR_IP>:<port>/druid/indexer/v1/worker/history?interval=<interval>
http://<OVERLORD_IP>:<port>/druid/indexer/v1/worker/history?interval=<interval>
```
default value of interval can be specified by setting `druid.audit.manager.auditHistoryMillis` (1 week if not configured) in overlord runtime.properties.

1
docs/content/misc/tasks.md
View File

@ -251,7 +251,6 @@ The indexing service can also run real-time tasks. These tasks effectively trans
"maxRowsInMemory": 500000,
"intermediatePersistPeriod": "PT10m",
"windowPeriod": "PT10m",
"basePersistDirectory": "\/tmp\/realtime\/basePersist",
"rejectionPolicy": {
"type": "serverTime"
}