[
https://issues.apache.org/jira/browse/MESOS-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111620#comment-15111620
]
Kapil Arya commented on MESOS-4430:
-----------------------------------
Some intial RRs (more to follow):
https://reviews.apache.org/r/42606/
https://reviews.apache.org/r/42623/
> Identify and change logging level for message that don't contain specific
> task/framework/slave info
> ---------------------------------------------------------------------------------------------------
>
> Key: MESOS-4430
> URL: https://issues.apache.org/jira/browse/MESOS-4430
> Project: Mesos
> Issue Type: Bug
> Reporter: Kapil Arya
> Assignee: Kapil Arya
> Labels: mesosphere
>
> The idea is to identify message such as:
> {code}
> mesos-slave[37891]: I0117 15:20:15.357344 37941 slave.cpp:4200] Received
> oversubscribable resources from the resource estimator
> mesos-slave[37891]: I0117 15:20:30.357959 37957 slave.cpp:4186] Querying
> resource estimator for oversubscribable resources
> {code}
> and remove them from default logging level. These messages don't provide any
> value to the sysadmin, etc., and fill up logs. In one incident, we observed
> over 12K lines of such message in the log over a 33hr run of a cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
