[
https://issues.apache.org/jira/browse/HBASE-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408716#comment-13408716
]
Matteo Bertozzi commented on HBASE-6233:
----------------------------------------
{quote}Do we want to incur extra complexity in our codebase for the hadoop
versions where there is no hdfs snapshot?{quote}
Are you talking about hdfs snapshot or hdfs hardlink?
I don't think that hbase can rely on hdfs snapshot (E.g. memstore, region info,
need to be handled in a special way)
For the missing hdfs hardlink support, I think that what I'm trying to propose
simplify a lot the snapshot, since we don't need to change the current code to
handle hfile deletions.
but I want some feedback on this, anyone has other suggestions/ideas?
> [brainstorm] snapshots: hardlink alternatives
> ---------------------------------------------
>
> Key: HBASE-6233
> URL: https://issues.apache.org/jira/browse/HBASE-6233
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Attachments: Restore-Snapshot-Hardlink-alternatives.pdf
>
>
> Discussion ticket around snapshots and hardlink alternatives.
> (See the HDFS-3370 discussion about hardlink and implementation problems)
> (taking for a moment WAL out of the discussion and focusing on hfiles)
> With hardlinks available taking snapshot will be fairly easy:
> * (hfiles are immutable)
> * hardlink to .snapshot/name to take snapshot
> * hardlink from .snapshot/name to restore the snapshot
> * No code change needed (on fs.delete() only one reference is deleted)
> but we don't have hardlinks, what are the alternatives?
--
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
