FrankChen021 commented on a change in pull request #11678: URL: https://github.com/apache/druid/pull/11678#discussion_r704891883
########## File path: docs/ingestion/tasks.md ########## @@ -355,6 +355,32 @@ The task context is used for various individual task configuration. The followin > When a task acquires a lock, it sends a request via HTTP and awaits until it > receives a response containing the lock acquisition result. > As a result, an HTTP timeout error can occur if `taskLockTimeout` is greater > than `druid.server.http.maxIdleTime` of Overlords. +## Task Logs + +Logs are created by ingestion tasks as they run. You can configure Druid to push these into a repository for long-term storage after they complete. + +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.indexer.task.baseTaskDir`](http://localhost:3000/docs/configuration/index.md#additional-peon-configuration). Review comment: ```suggestion 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.indexer.task.baseTaskDir`](../configuration/index.md#additional-peon-configuration). ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
