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

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

Github user revans2 commented on the pull request:

    https://github.com/apache/storm/pull/822#issuecomment-163713836
  
    @harshach and @erikdw can you explain the exact use cases you are concerned 
about?  From previous interactions it feels like you are concerned about storm 
on slider on YARN and storm on mesos respectively.  So the fix is to place the 
logs in a configurable place that other tools can get access to?
    
    I just want to be sure I understand the use case so I can properly address 
those concerns.  We can move the worker-artifacts dir to be in a configurable 
location.  That should be totally doable.  I wouldn't really want them all to 
be under storm.log.dir, as @zhuoliu pointed out there are more than just logs 
stored here.  As part of this change we essentially upgraded the logs to be 
application metadata that can have limits placed on them and managed.  But if 
you really want it based off of storm.log.dir as a default it is not a deal 
breaker.


> 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