[MESOS-1933] Give better guidance when the replicated log only has EMPTY members

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: replicated log
• Assignee: Unassigned
• Reporter: Bill Farner
• Created: 15/Oct/14 22:49
• Updated: 16/Oct/14 16:39
• Resolved: 16/Oct/14 16:39

Description

When a replicated log consumer attempts to lead, we can be stuck in a state where only EMPTY replicas are present. In this case, we see an endless stream of log entries like:

I1015 21:18:06.027016 27634 replica.cpp:638] Replica in EMPTY status received a broadcasted recover request
I1015 21:18:06.027216 27634 recover.cpp:188] Received a recover response from a replica in EMPTY status

The answer to this is (always, AFAIK) to initialize the log on the EMPTY replica(s). However, it's not obvious to draw that conclusion from the log messages.

Please make the log message more informative to help users figure out how to course-correct.

Issue Links

• duplicates: MESOS-1703 better error message when replicated log hasn't been initialized