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

ASF GitHub Bot commented on FLINK-4269:
---------------------------------------

GitHub user aditivin opened a pull request:

    https://github.com/apache/flink/pull/2307

    [FLINK-4269] Decrease log level in RuntimeMonitorHandler

    @uce - I changed the log level to DEBUG in RuntimeMonitorHandler. 
    
    PS - This is my first contribution, please forgive any mistakes :)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aditivin/flink FLINK-4269

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2307.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2307
    
----
commit 9e75a10b9f9e613ddb31dbdc5fc631fe5cfbb7eb
Author: Aditi Viswanathan <aditi...@gmail.com>
Date:   2016-07-29T04:22:46Z

    Merge remote-tracking branch 'apache/master'

commit 250764709e940029056ac2ddd0e5532a69133471
Author: Aditi Viswanathan <aditi...@gmail.com>
Date:   2016-07-29T04:46:52Z

    [FLINK-4269] [webfrontend] Decrease log level in RuntimeMonitorHandler

----


> Decrease log level in RuntimeMonitorHandler
> -------------------------------------------
>
>                 Key: FLINK-4269
>                 URL: https://issues.apache.org/jira/browse/FLINK-4269
>             Project: Flink
>          Issue Type: Improvement
>          Components: Webfrontend
>    Affects Versions: 1.1.0
>            Reporter: Ufuk Celebi
>            Priority: Minor
>
> Having a browser window open which points to a page of an unavailable job 
> (for example from a previous cluster setup) leads to many log warning 
> messages like this in the job manager log file:
> {code}
> 2016-06-30 10:50:55,812 WARN  
> org.apache.flink.runtime.webmonitor.RuntimeMonitorHandler     - Error while 
> handling request
> org.apache.flink.runtime.webmonitor.NotFoundException: Could not find job 
> with id 343bd3c0c7415370d79e04f305b5a2e9
>       at 
> org.apache.flink.runtime.webmonitor.handlers.AbstractExecutionGraphRequestHandler.handleRequest(AbstractExecutionGraphRequestHandler.java:58)
>       at 
> org.apache.flink.runtime.webmonitor.RuntimeMonitorHandler.respondAsLeader(RuntimeMonitorHandler.java:135)
>       at 
> org.apache.flink.runtime.webmonitor.RuntimeMonitorHandler.channelRead0(RuntimeMonitorHandler.java:112)
>       at 
> org.apache.flink.runtime.webmonitor.RuntimeMonitorHandler.channelRead0(RuntimeMonitorHandler.java:60)
>       at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
>       at io.netty.handler.codec.http.router.Handler.routed(Handler.java:62)
>       at 
> io.netty.handler.codec.http.router.DualAbstractHandler.channelRead0(DualAbstractHandler.java:57)
>       at 
> io.netty.handler.codec.http.router.DualAbstractHandler.channelRead0(DualAbstractHandler.java:20)
>       at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
>       at 
> org.apache.flink.runtime.webmonitor.HttpRequestHandler.channelRead0(HttpRequestHandler.java:104)
>       at 
> org.apache.flink.runtime.webmonitor.HttpRequestHandler.channelRead0(HttpRequestHandler.java:65)
>       at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
>       at 
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:242)
>       at 
> io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:147)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
>       at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
>       at 
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:847)
>       at 
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
>       at 
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
>       at 
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
>       at 
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
>       at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
>       at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
>       at 
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
> {code}
> Since the REST API calls are refreshed every X seconds, this can lead to 
> quite some log pollution. We might consider decreasing the log level to DEBUG 
> or TRACE even.



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

Reply via email to