[
https://issues.apache.org/jira/browse/HBASE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891869#comment-13891869
]
Hadoop QA commented on HBASE-10347:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12627072/hbase-10347_redo_v6.patch
against trunk revision .
ATTACHMENT ID: 12627072
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 17 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestAssignmentManager
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8601//console
This message is automatically generated.
> HRegionInfo changes for adding replicaId and MetaEditor/MetaReader changes
> for region replicas
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-10347
> URL: https://issues.apache.org/jira/browse/HBASE-10347
> Project: HBase
> Issue Type: Sub-task
> Components: Region Assignment
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.99.0
>
> Attachments: hbase-10347_redo_v4.patch, hbase-10347_redo_v5.patch,
> hbase-10347_redo_v6.patch
>
>
> As per parent jira, the cleanest way to add region replicas we think is to
> actually create one more region per replica per primary region. So for
> example, if a table has 10 regions with replication = 3, the table would
> indeed be created with 30 regions. These regions will be handled and assigned
> individually for AM purposes.
> We can add replicaId to HRegionInfo to indicate the replicaId, and use this
> to differentiate different replicas of the same region. So, primary replica
> would have replicaId = 0, and the others will have replicaId > 0.
> These replicas will share the same regionId prefix, but differ in an appended
> replicaId. The primary will not contain the replicaId so that no changes
> would be needed for existing tables.
> In meta, the replica regions are kept in the same row as the primary ( so for
> above example, there will be 10 rows in meta). The servers for the replicas
> are kept in columns like "server+replicaId".
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
