hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10572) Create an IntegrationTest for region replicas
Date Mon, 10 Mar 2014 17:35:42 GMT

     [ https://issues.apache.org/jira/browse/HBASE-10572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Devaraj Das updated HBASE-10572:
--------------------------------

    Attachment: 10572-add.txt

Not sure if I missed something but passing the argument {noformat}-DIntegrationTestTimeBoundedRequestsWithRegionReplicas.region_replication{noformat}
didn't reflect in the #replicas for the test table. The test table always gets created with
1 replica.

I had to make the one line change as in the patch attached for the argument to have an effect
(in the earlier patch, hbase-10572_v0.patch, the region_replication would be set in a different
place via modifyTable).

Also, should we fail the test after "READ FAILURE" is > 0?

> Create an IntegrationTest for region replicas
> ---------------------------------------------
>
>                 Key: HBASE-10572
>                 URL: https://issues.apache.org/jira/browse/HBASE-10572
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: hbase-10070
>
>         Attachments: 10572-add.txt, hbase-10572_v0.patch, hbase-10572_v1.patch
>
>
> We should add an integration test for testing reads from replicas with chaos monkey.

> I am thinking of a test which: 
>  - Creates a table with region replication
>  - Writes some data to a table with many regions per server. Ensures that the replicas
sees the data.
>  - Does time bounded gets (5 sec, etc) with timeline consistency. Failing to complete
the reads with a smaller latency will fail the test
>  - Runs Chaos Monkey to kill the region servers, master and runs balance. We do not want
other CM actions (flush, snapshot, etc) 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message