Return-Path: X-Original-To: apmail-mesos-issues-archive@minotaur.apache.org Delivered-To: apmail-mesos-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 730C011E11 for ; Fri, 27 Jun 2014 03:50:25 +0000 (UTC) Received: (qmail 42563 invoked by uid 500); 27 Jun 2014 03:50:25 -0000 Delivered-To: apmail-mesos-issues-archive@mesos.apache.org Received: (qmail 42531 invoked by uid 500); 27 Jun 2014 03:50:24 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 42507 invoked by uid 99); 27 Jun 2014 03:50:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 03:50:24 +0000 Date: Fri, 27 Jun 2014 03:50:24 +0000 (UTC) From: "Dominic Hamon (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MESOS-1502) expose message event queue size from libprocess MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045488#comment-14045488 ] Dominic Hamon commented on MESOS-1502: -------------------------------------- https://reviews.apache.org/r/22817/ https://reviews.apache.org/r/22757/ > expose message event queue size from libprocess > ----------------------------------------------- > > Key: MESOS-1502 > URL: https://issues.apache.org/jira/browse/MESOS-1502 > Project: Mesos > Issue Type: Improvement > Reporter: Dominic Hamon > Fix For: 0.21.0 > > > We currently expose the event queue size for the master through libprocess. Ideally we would expose the message event queue size as separate from dispatch events which are largely internal and uninteresting. > We might consider exposing each type of event as a separate count. -- This message was sent by Atlassian JIRA (v6.2#6252)