You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Armand Grillet (JIRA)" <ji...@apache.org> on 2017/12/13 19:50:00 UTC

[jira] [Comment Edited] (MESOS-7361) Command checks via agent pollute agent logs.

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

Armand Grillet edited comment on MESOS-7361 at 12/13/17 7:49 PM:
-----------------------------------------------------------------

https://reviews.apache.org/r/64575/


was (Author: armandgrillet):
https://reviews.apache.org/r/64575/
https://reviews.apache.org/r/64576/

> Command checks via agent pollute agent logs.
> --------------------------------------------
>
>                 Key: MESOS-7361
>                 URL: https://issues.apache.org/jira/browse/MESOS-7361
>             Project: Mesos
>          Issue Type: Improvement
>          Components: agent
>            Reporter: Alexander Rukletsov
>            Assignee: Armand Grillet
>              Labels: check, health-check, mesosphere
>
> Command checks via agent leverage debug container API of the agent to start checks. Each such invocation triggers a bunch of logs on the agent, because the API was not originally designed with periodic invocations in mind. We should find a way to avoid excessive logging on the agent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)