[
https://issues.apache.org/jira/browse/HBASE-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174189#comment-15174189
]
Enis Soztutar commented on HBASE-15321:
---------------------------------------
bq. U can have this code in ur setup. Make the HRegionInfo to set it as a non
primary replica id.. Yes this HRegion instance will give out of date data just
like non primary replicas. Setting to non primary make it to be readOnly.
Yes, we are doing exactly what this issue tries to solve (having read-only view
of the region and file system) for secondary region replicas. The secondaries
cannot do any mutations to the file structures, etc.
We can generalize this logic if needed.
> 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)
