[jira] [Commented] (HBASE-9204) An Offline SplitParent Region can be assigned breaking split references

["ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>]

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

ramkrishna.s.vasudevan commented on HBASE-9204:
-----------------------------------------------

Correct me if am wrong.  If i remember correctly this scenario would be handled in master restart.
{code}
// Fixing up missing daughters if any
    status.setStatus("Fixing up missing daughters");
    fixupDaughters(status);
{code}
I need to accept that its long since i worked on issues in this area.  But I had a feel that this piece of code would handle it.  May be something changed in recent code?
I agree that AM should handle this and not the RegionServer.
                
> An Offline SplitParent Region can be assigned breaking split references
> -----------------------------------------------------------------------
>
>                 Key: HBASE-9204
>                 URL: https://issues.apache.org/jira/browse/HBASE-9204
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 0.98.0, 0.95.1, 0.94.10
>            Reporter: Matteo Bertozzi
>            Priority: Blocker
>         Attachments: HBASE-9294-0.94-v0.patch
>
>
> An offline split parent region can be assigned by using 'assign' from shell.
> This may trigger a compaction on the split parent region that should be offline, breaking the references of the two daughters.
> The easy way to test this is:
>  * disable compactions
>  * create a table and insert some row
>  * split
>  * shutdown the master (otherwise there's a state checked inside the AssignmentManager)
>  * start the master
>  * assign the region marked as OFFLINE => true, SPLIT => true (the compaction on region startup will probably break the reference of the two  daughters)

--
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