[
https://issues.apache.org/jira/browse/HBASE-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171492#comment-15171492
]
Anoop Sam John commented on HBASE-15321:
----------------------------------------
On the patch .
So you add a new state to HRegion whether it is read only or not.
Actually we can set on region that it is write only. So then I can see it wont
try for dir cleanup and all. Only diff is even if it is open with write
disabled, it will try for replay log. I can see the read only check is added
there. So that comes as a reason for new state? If we add this new state, then
when called write state enabled, it should not be allowed if read only is true.
> Ability to open a HRegion from hdfs snapshot.
> ---------------------------------------------
>
> Key: HBASE-15321
> URL: https://issues.apache.org/jira/browse/HBASE-15321
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 2.0.0
> Reporter: churro morales
> Fix For: 2.0.0
>
> Attachments: HBASE-15321-v1.patch, HBASE-15321-v2.patch,
> HBASE-15321-v3.patch, HBASE-15321.patch
>
>
> Now that hdfs snapshots are here, we started to run our mapreduce jobs over
> hdfs snapshots. The thing is, hdfs snapshots are read-only point-in-time
> copies of the file system. Thus we had to modify the section of code that
> initialized the region internals in HRegion. We have to skip cleanup of
> certain directories if the HRegion is backed by a hdfs snapshot. I have a
> patch for trunk with some basic tests if folks are interested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
