mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Pronin (JIRA)" <>
Subject [jira] [Created] (MESOS-7973) Non-leading VOTING replica catch-up
Date Wed, 13 Sep 2017 16:23:00 GMT
Ilya Pronin created MESOS-7973:

             Summary: Non-leading VOTING replica catch-up
                 Key: MESOS-7973
             Project: Mesos
          Issue Type: Improvement
          Components: replicated log
            Reporter: Ilya Pronin
            Assignee: Ilya Pronin

Currently it is not possible to perform consistent reads from non-leading replicas due to
the fact that if a non-leading replica is partitioned it may miss some log positions and will
not make any attempt to “fill” those holes.

If a non-leading replica could catch-up missing log positions it would be able to serve eventually
consistent reads to the framework. This would make it possible to do additional work on non-leading
framework replicas (e.g. offload some reading from a leader to standbys or reduce failover
time by keeping in-memory storage represented by the log “hot”).

Design doc:

This message was sent by Atlassian JIRA

View raw message