[
https://issues.apache.org/jira/browse/HBASE-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769148#comment-13769148
]
Hudson commented on HBASE-9525:
-------------------------------
FAILURE: Integrated in hbase-0.96 #57 (See
[https://builds.apache.org/job/hbase-0.96/57/])
HBASE-9525 "Move" region right after a region split is dangerous (jxiang: rev
1523836)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionMergeTransactionOnCluster.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java
> "Move" region right after a region split is dangerous
> -----------------------------------------------------
>
> Key: HBASE-9525
> URL: https://issues.apache.org/jira/browse/HBASE-9525
> Project: HBase
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Jimmy Xiang
> Fix For: 0.98.0, 0.96.0
>
> Attachments: logs.txt, trunk-9525.patch
>
>
> I ran into a situation where the CM issued a move for a region just after a
> region was split. The master went bonkers since the master honored the CM
> request, and assigned the split region, but subsequently all the region state
> assumptions on this (split)region was messed up. I started seeing log lines
> lines like "THIS SHOULD NOT HAPPEN". Also, it created other problems - a
> compaction on original region happened on the new assignee, and then the
> daughter regions started seeing issues to do with store files missing, etc.,
> etc.
> I will upload the logs shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
