[ 
https://issues.apache.org/jira/browse/STORM-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051801#comment-15051801
 ] 

ASF GitHub Bot commented on STORM-901:
--------------------------------------

Github user harshach commented on the pull request:

    https://github.com/apache/storm/pull/822#issuecomment-163776916
  
    @revans2 I want user experience to be consistent . I.e when they configure 
storm.log.dir , the logs to be appear in configured storm.log.dir , not some of 
the logs in storm.log.dir and others in storm-local/worker-artifacts. Its hard 
to understand why they are ending up there. In some cases storm-local dir might 
only accessed by linux user "storm" who is running the daemons. My request is 
to keep the current hierarchical dir that we've right now but move all the logs 
to configured storm.log.dir not have it in storm-local/worker-artifacts. Not 
sure if this requires lot of changes for this patch.


> 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)

Reply via email to