You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2015/10/07 23:42:27 UTC
[jira] [Commented] (MESOS-3417) Log source address replicated log
recieved broadcasts
[ https://issues.apache.org/jira/browse/MESOS-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947650#comment-14947650 ]
Neil Conway commented on MESOS-3417:
------------------------------------
https://reviews.apache.org/r/39104/
> 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.23.0, 0.24.0
> Environment: Mesos 0.23
> Reporter: Cody Maloney
> Assignee: Neil Conway
> Priority: Minor
> Labels: mesosphere, newbie
>
> 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)