[jira] [Commented] (STORM-412) Allow users to modify logging levels of running topologies.

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

Github user revans2 commented on the pull request:

    https://github.com/apache/storm/pull/766#issuecomment-145252754
  
    I am still +1 on this.  @kishorvpatil The merge conflict is very minor in the commands list in storm.py, please upmerge.
    
    @Parth-Brahmbhatt I really would like to get this in soon.  Please take a look at the fix so I can pull this in.


> Allow users to modify logging levels of running topologies.
> -----------------------------------------------------------
>
>                 Key: STORM-412
>                 URL: https://issues.apache.org/jira/browse/STORM-412
>             Project: Apache Storm
>          Issue Type: Improvement
>            Reporter: Robert Joseph Evans
>
> It really would be great to be able to turn on debug logging for different parts of an already running topology, and then turn them off again later.  Or even better if they could turn it on for just a few workers, so we don't flood the logs for a very large topology.
> logback already has the ability to refresh its config periodically so really what we needs is some code to generate logback configs on the fly based off of the currently desired user settings, and API to modify those dynamically, and a way to distribute those configs/settings to the supervisors.  I am not too concerned about persisting these settings long term.  If nimbus goes down and they reset back to default, I think that would be OK.
> For the distribution of the configs I think it would be best to setup a RESTful web service that is a part of nimbus.  logback already supports using http to download configs.  The service could use the cached logging settings for a given topology, or individual worker and the URL of the request to generate a logging config on the fly for a specific worker.  As for the APIs I think a few new thrift calls to nimbus would be good, a command line tool, and possibly something on the UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)