[
https://issues.apache.org/jira/browse/HBASE-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399946#comment-13399946
]
David S. Wang commented on HBASE-6258:
--------------------------------------
I see this comment from HBASE-6158:
https://issues.apache.org/jira/browse/HBASE-6158?focusedCommentId=13288890&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13288890
> Is this change incompatible for rolling upgrade?
I don't think so. These are temporary work folders which get cleaned up
routinely and particularly at Region Server (re)start for each region through
HRegion.initialize().
However, a possible side effect could be that "merges" and "splits" folders
created by pre-upgrade code (which somehow did not get cleaned up during a
shutdown) may continue to exist on the file system as the cleanup code would no
longer be looking for them. But this is better fixed in the upgrade scripts by
deleting these folders if they are found to be a work folder instead of a CF
container folder.
I'll continue the conversation over on HBASE-6158.
> Backport some region splitting fixes into 0.90.7
> ------------------------------------------------
>
> Key: HBASE-6258
> URL: https://issues.apache.org/jira/browse/HBASE-6258
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.90.6
> Reporter: David S. Wang
> Assignee: David S. Wang
> Attachments: HBASE-4816+4881+5189+6158.patch
>
>
> Issue tracking backport of some relatively small region splitting fixes into
> 0.90.7:
> HBASE-4816: Regionserver wouldn't go down because split happened exactly at
> same time we issued bulk user region close call on our way out - fixed in 0.92
> HBASE-4881: Unhealthy region is on service caused by rollback of region
> splitting - fixed in 0.92
> HBASE-5189: Add metrics to keep track of region-splits in RS - fixed in 0.94
> HBASE-6158: Data loss if the words 'merges' or 'splits' are used as Column
> Family name - fixed in 0.92 and 0.94
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
