[MESOS-3417] Log source address replicated log recieved broadcasts

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.23.0, 0.24.0
• Fix Version/s: 0.26.0
• Component/s: replicated log
• Labels: mesosphere newbie

Environment

Mesos 0.23

• Sprint: Mesosphere Sprint 20
• Story Points: 2
• Assignee: Neil Conway
• Reporter: Cody Maloney
• Shepherd: Adam B
• Created: 12/Sep/15 05:55
• Updated: 26/Nov/18 12:21
• Resolved: 26/Nov/18 12:21

Description

Currently Mesos doesn't log what machine a replicated log status broadcast was recieved from:

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

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