You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/10/16 00:50:33 UTC

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

Bill Farner created MESOS-1933:
----------------------------------

             Summary: Give better guidance when the replicated log only has EMPTY members
                 Key: MESOS-1933
                 URL: https://issues.apache.org/jira/browse/MESOS-1933
             Project: Mesos
          Issue Type: Improvement
          Components: replicated log
            Reporter: Bill Farner


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:

{noformat}
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
{noformat}

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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)