zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3140) Allow Followers to host Observers
Date Sat, 15 Sep 2018 00:32:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615533#comment-16615533

Hadoop QA commented on ZOOKEEPER-3140:

-1 overall.  GitHub Pull Request  Build

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 22 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 3.0.1) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2184//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2184//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2184//console

This message is automatically generated.

> Allow Followers to host Observers
> ---------------------------------
>                 Key: ZOOKEEPER-3140
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3140
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: Brian Nixon
>            Assignee: Brian Nixon
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Observers function simple as non-voting members of the ensemble, sharing the Learner
interface with Followers and holding only a slightly difference internal pipeline. Both maintain
connections along the quorum port with the Leader by which they learn of all new proposals
on the ensemble. 
>  There are benefits to allowing Observers to connect to the Followers to plug into the
commit stream in addition to connecting to the Leader. It shifts the burden of supporting
Observers off the Leader and allow it to focus on coordinating the commit of writes. This
means better performance when the Leader is under high load, particularly high network load
such as can happen after a leader election when many Learners need to sync. It also reduces
the total network connections maintained on the Leader when there are a high number of observers.
One the other end, Observer availability is improved since it will take shorter time for a
high number of Observers to finish syncing and start serving client traffic.
>  The current implementation only supports scaling the number of Observers into the hundreds
before performance begins to degrade. By opening up Followers to also host Observers, over
a thousand observers can be hosted on a typical ensemble without major negative impact under
both normal operation and during post-leader election sync.

This message was sent by Atlassian JIRA

View raw message