[
https://issues.apache.org/jira/browse/STORM-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052031#comment-15052031
]
ASF GitHub Bot commented on STORM-901:
--------------------------------------
Github user unsleepy22 commented on the pull request:
https://github.com/apache/storm/pull/822#issuecomment-163813319
@revans2 @zhuoliu This solution looks good to me too.
My initial concern was sort of like @erikdw 's use case. And usually files
in logs directory do a rolling update/delete(maybe by a cron job), while we may
not want a rolling delete for metadata(or at least different delete stragety),
so it's good to add an extra config in storm.yaml to specify this directory.
> Worker Artifacts Directory
> --------------------------
>
> Key: STORM-901
> URL: https://issues.apache.org/jira/browse/STORM-901
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Zhuo Liu
> Fix For: 0.11.0
>
> Attachments: daemon-logs-view.png, worker-logs-view.png
>
>
> At Yahoo we have added in one separate directory that not only stores each
> topology's every worker's log files, but also provides a place where the
> worker can place other files which helps with debugging (gc logs and heap
> dump files). It is a new directory that soft-links to the current working
> directory of the worker process. The oldest files in each worker's artifacts
> directory are cleaned up if they get too large (exceeding the per-dir quota
> or the global quota).
> This work is already done, but needs to be put back into open source.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
