[
https://issues.apache.org/jira/browse/MESOS-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505843#comment-14505843
]
Benjamin Mahler commented on MESOS-2498:
----------------------------------------
{quote}It doesn't even specify the source of the request{quote}
Ideally the source is logged as well: MESOS-2519
{{/state.json}} has adverse effects on the master's performance on large
clusters (MESOS-2353), so you may want to be careful about hitting it
frequently from your tooling and libraries. In general, there's value in having
visibility into the volume of the various http requests (i.e. metrics may be a
reasonable alternative to explore if the logging is really an issue).
> Change Http Request log level to VLOG(1)
> ----------------------------------------
>
> Key: MESOS-2498
> URL: https://issues.apache.org/jira/browse/MESOS-2498
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Reporter: haosdent
> Assignee: haosdent
> Priority: Minor
> Attachments: MESOS-2498.patch
>
>
> Hello, I use mesos-go. But I find a lot unnecessary info log:
> {quote}
> HTTP request for '/master/state.json'
> {quote}
> These logs make a lot of noise, so I suggest to change the level from INFO to
> VLOG(1).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
