From 222a13e4011a73cdcc995a51f8fa7433e68cf142 Mon Sep 17 00:00:00 2001 From: Himanshu Date: Fri, 2 Feb 2018 14:16:43 -0600 Subject: [PATCH] Use httpRemote and not remoteHttp for using HTTP Tasks Mgmt (#5334) --- docs/content/configuration/indexing-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/configuration/indexing-service.md b/docs/content/configuration/indexing-service.md index 417dc6dcc37..38cbdc87a9a 100644 --- a/docs/content/configuration/indexing-service.md +++ b/docs/content/configuration/indexing-service.md @@ -94,7 +94,7 @@ Store task logs in HDFS. |Property|Description|Default| |--------|-----------|-------| -|`druid.indexer.runner.type`|Choices "local" or "remote". Indicates whether tasks should be run locally or in a distributed environment. Experimental task runner "remoteHttp" is also available which is same as "remote" but uses HTTP to interact with Middle Manaters instead of Zookeeper.|local| +|`druid.indexer.runner.type`|Choices "local" or "remote". Indicates whether tasks should be run locally or in a distributed environment. Experimental task runner "httpRemote" is also available which is same as "remote" but uses HTTP to interact with Middle Manaters instead of Zookeeper.|local| |`druid.indexer.storage.type`|Choices are "local" or "metadata". Indicates whether incoming tasks should be stored locally (in heap) or in metadata storage. Storing incoming tasks in metadata storage allows for tasks to be resumed if the overlord should fail.|local| |`druid.indexer.storage.recentlyFinishedThreshold`|A duration of time to store task results.|PT24H| |`druid.indexer.queue.maxSize`|Maximum number of active tasks at one time.|Integer.MAX_VALUE|