From cae9cbd7d7c3419be8db6276b50c22cfb770b8ac Mon Sep 17 00:00:00 2001 From: Peter Marshall Date: Tue, 13 Feb 2024 13:20:09 +0000 Subject: [PATCH] Update tasks.md (#15887) Remove erroneous white space causing render issues on this page. --- docs/ingestion/tasks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ingestion/tasks.md b/docs/ingestion/tasks.md index d9f0758ede6a..855c98243476 100644 --- a/docs/ingestion/tasks.md +++ b/docs/ingestion/tasks.md @@ -404,7 +404,7 @@ Logs are created by ingestion tasks as they run. You can configure Druid to push Once the task has been submitted to the Overlord it remains `WAITING` for locks to be acquired. Worker slot allocation is then `PENDING` until the task can actually start executing. -The task then starts creating logs in a local directory of the middle manager (or indexer) in a `log` directory for the specific `taskId` at [`druid.worker.baseTaskDirs`] (../configuration/index.md#middlemanager-configuration). +The task then starts creating logs in a local directory of the middle manager (or indexer) in a `log` directory for the specific `taskId` at [`druid.worker.baseTaskDirs`](../configuration/index.md#middlemanager-configuration). When the task completes - whether it succeeds or fails - the middle manager (or indexer) will push the task log file into the location specified in [`druid.indexer.logs`](../configuration/index.md#task-logging).