hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11842) Integration test for async wal replication to secondary regions
Date Sat, 21 Feb 2015 02:23:11 GMT

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

Enis Soztutar commented on HBASE-11842:

bq. Second line above has 'hbase.' prefix. Should it be consistent with the style of the other
options ?
The usage of "hbase" prefix is coming from the base class. We should have standardized it,
but unfortunately we did not. We can fix it in another patch. 
bq. Why factor of 0.9 is used above ?
0.9 is used since the run time is just a soft bound on how long the test should run. It is
iterative, so expectation is that it will not iterate more if it is around %90 done. 

> Integration test for async wal replication to secondary regions
> ---------------------------------------------------------------
>                 Key: HBASE-11842
>                 URL: https://issues.apache.org/jira/browse/HBASE-11842
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.1.0
>         Attachments: hbase-11842_v1.patch, hbase-11842_v2.patch
> We should add an integration test to cover async wal replication to secondary regions.

> Async wal replication to region replicas has been committed (HBASE-11568) and flush /compaction
handling (HBASE-11569) and failover handling for secondary region replicas (HBASE-11580) is
in the works.  
> The test can use LoadTestTool over a table with region replicas. We can write to the
primary regions, and read from the secondary region replicas in reader threads to do the verification.

This message was sent by Atlassian JIRA

View raw message