mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cody Maloney (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MESOS-3417) Log source address replicated log recieved broadcasts
Date Sat, 12 Sep 2015 05:55:46 GMT
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)

Mime
View raw message