You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kunal Thakar (JIRA)" <ji...@apache.org> on 2016/09/30 19:20:20 UTC

[jira] [Commented] (MESOS-6295) Excessive logging on agent when oversubscription modules are attached

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

Kunal Thakar commented on MESOS-6295:
-------------------------------------

Patch: https://reviews.apache.org/r/52438/

> Excessive logging on agent when oversubscription modules are attached 
> ----------------------------------------------------------------------
>
>                 Key: MESOS-6295
>                 URL: https://issues.apache.org/jira/browse/MESOS-6295
>             Project: Mesos
>          Issue Type: Bug
>          Components: oversubscription
>            Reporter: Kunal Thakar
>              Labels: module, newbie
>
> The mesos agent is logging a INFO log in the agent that prints out the number of QoS corrections received from the module [1]. By default, this method gets called in a tight loop, which results in the logs getting flooded with noise.
> {code}
> mesos-slave[14591]: I0930 17:31:19.278774 14598 slave.cpp:5049] Received 0 QoS corrections
> mesos-slave[14591]: I0930 17:31:19.280088 14602 slave.cpp:5049] Received 0 QoS corrections
> mesos-slave[14591]: I0930 17:31:19.281497 14599 slave.cpp:5049] Received 0 QoS corrections
> mesos-slave[14591]: I0930 17:31:19.282856 14614 slave.cpp:5049] Received 0 QoS corrections
> {code}
> Even after reducing the QoS checking frequency, this line does not make for a good INFO log as it is periodic. Can we change it to only log when there are non zero number of corrections received from the module? I can send a patch if this is acceptable.
> [1] https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L5523



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