surekhasaharan commented on a change in pull request #6592: tasks tables in metadata storage are not cleared URL: https://github.com/apache/incubator-druid/pull/6592#discussion_r235197111
########## File path: docs/content/configuration/index.md ########## @@ -525,12 +525,12 @@ If you are running the indexing service in remote mode, the task logs must be st |--------|-----------|-------| |`druid.indexer.logs.type`|Choices:noop, s3, azure, google, hdfs, file. Where to store task logs|file| -You can also configure the Overlord to automatically retain the task logs only for last x milliseconds by configuring following additional properties. +You can also configure the Overlord to automatically retain the task logs in log directory and task-related metadata storage tables only for last x milliseconds by configuring following additional properties. Caution: Automatic log file deletion typically works based on log file modification timestamp on the backing store, so large clock skews between druid nodes and backing store nodes might result in un-intended behavior. |Property|Description|Default| |--------|-----------|-------| -|`druid.indexer.logs.kill.enabled`|Boolean value for whether to enable deletion of old task logs. |false| +|`druid.indexer.logs.kill.enabled`|Boolean value for whether to enable deletion of old task logs. If set to true, overlord will submit tasks periodically based on `delay` specified. These kill tasks will delete task logs from log directory and tasks and tasklogs table in metadata storage except for the last `durationToRetain` period. |false| |`druid.indexer.logs.kill.durationToRetain`| Required if kill is enabled. In milliseconds, task logs to be retained created in last x milliseconds. |None| Review comment: If this behavior is also getting changed, please add doc here as well, something like "task logs and task-related metadata storage tables to be retained created in last x milliseconds" ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
