mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7361) Command checks via agent pollute agent logs.
Date Fri, 10 Nov 2017 17:08:00 GMT

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

Alexander Rukletsov commented on MESOS-7361:
--------------------------------------------

{noformat}
Commit: d9f95056e0dbdf8bd4aad1139b91945def1f9f8a [d9f9505]
Author: Armand Grillet <agrillet@mesosphere.io>
Date: 10 November 2017 at 18:02:24 GMT+1
Committer: Alexander Rukletsov <alexr@apache.org>

Added context to agent processing calls.

This changes adds context information to log entries for agent HTTP
API handlers where possible. For example, container ID when processing
requests related to nested containers, or target path when processing
requests related to files.

Review: https://reviews.apache.org/r/63694/
{noformat}

> 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)

Mime
View raw message