Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 10 Oct 2016 19:57:21 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12682280.1386031479000.786111.1476129441794@Atlassian.JIRA>
In-Reply-To: <JIRA.12682280.1386031479000@Atlassian.JIRA>
References: <JIRA.12682280.1386031479000@Atlassian.JIRA> <JIRA.12682280.1386031479988@arcas>
Subject: [jira] [Commented] (HBASE-10070) HBase read high-availability using
 timeline-consistent region replicas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Oct 2016 19:57:23 -0000


    [ https://issues.apache.org/jira/browse/HBASE-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563309#comment-15563309 ] 

Enis Soztutar commented on HBASE-10070:
---------------------------------------

bq. Is there any documentation about how this feature affect co-processors, specially endpoint co-processors?
No effect to endpoint coprocessors. Only the get requests or scan requests are performed with backup RPC requests to replicas. The endpoint RPCs will only go to the primary replica. The coprocessors which inject into preGet() etc will get called though, whenever the client does an RPC to the primary replica or secondary replicas. 


> HBase read high-availability using timeline-consistent region replicas
> ----------------------------------------------------------------------
>
>                 Key: HBASE-10070
>                 URL: https://issues.apache.org/jira/browse/HBASE-10070
>             Project: HBase
>          Issue Type: New Feature
>          Components: Admin, API, LatencyResilience
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>              Labels: needs_releasenote
>             Fix For: 2.0.0, 1.2.0
>
>         Attachments: HighAvailabilityDesignforreadsApachedoc.pdf
>
>
> In the present HBase architecture, it is hard, probably impossible, to satisfy constraints like 99th percentile of the reads will be served under 10 ms. One of the major factors that affects this is the MTTR for regions. There are three phases in the MTTR process - detection, assignment, and recovery. Of these, the detection is usually the longest and is presently in the order of 20-30 seconds. During this time, the clients would not be able to read the region data.
> However, some clients will be better served if regions will be available for reads during recovery for doing eventually consistent reads. This will help with satisfying low latency guarantees for some class of applications which can work with stale reads.
> For improving read availability, we propose a replicated read-only region serving design, also referred as secondary regions, or region shadows. Extending current model of a region being opened for reads and writes in a single region server, the region will be also opened for reading in region servers. The region server which hosts the region for reads and writes (as in current case) will be declared as PRIMARY, while 0 or more region servers might be hosting the region as SECONDARY. There may be more than one secondary (replica count > 2).
> Will attach a design doc shortly which contains most of the details and some thoughts about development approaches. Reviews are more than welcome. 
> We also have a proof of concept patch, which includes the master and regions server side of changes. Client side changes will be coming soon as well. 


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