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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
