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 7CC8810481 for ; Sat, 12 Sep 2015 05:55:46 +0000 (UTC) Received: (qmail 54730 invoked by uid 500); 12 Sep 2015 05:55:46 -0000 Delivered-To: apmail-mesos-issues-archive@mesos.apache.org Received: (qmail 54664 invoked by uid 500); 12 Sep 2015 05:55:46 -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 54654 invoked by uid 99); 12 Sep 2015 05:55:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Sep 2015 05:55:46 +0000 Date: Sat, 12 Sep 2015 05:55:46 +0000 (UTC) From: "Cody Maloney (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MESOS-3417) Log source address replicated log recieved broadcasts MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Cody Maloney created MESOS-3417: ----------------------------------- Summary: Log source address replicated log recieved broadcasts Key: MESOS-3417 URL: https://issues.apache.org/jira/browse/MESOS-3417 Project: Mesos Issue Type: Improvement Components: replicated log Affects Versions: 0.24.0, 0.23.0 Environment: Mesos 0.23 Reporter: Cody Maloney Assignee: Adam B Priority: Minor Currently Mesos doesn't log what machine a replicated log status broadcast was recieved from: {code} Sep 11 21:41:14 master-01 mesos-master[15625]: I0911 21:41:14.320164 15637 replica.cpp:641] Replica in EMPTY status received a broadcasted recover request Sep 11 21:41:14 master-01 mesos-dns[15583]: I0911 21:41:14.321097 15583 detect.go:118] ignoring children-changed event, leader has not changed: /mesos Sep 11 21:41:14 master-01 mesos-master[15625]: I0911 21:41:14.353914 15639 replica.cpp:641] Replica in EMPTY status received a broadcasted recover request Sep 11 21:41:14 master-01 mesos-master[15625]: I0911 21:41:14.479132 15639 replica.cpp:641] Replica in EMPTY status received a broadcasted recover request {code} It would be really useful for debugging replicated log startup issues to have info about where the message came from (libprocess address, ip, or hostname) the message came from -- This message was sent by Atlassian JIRA (v6.3.4#6332)