[
https://issues.apache.org/jira/browse/HBASE-7321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537405#comment-13537405
]
Jonathan Hsieh commented on HBASE-7321:
---------------------------------------
In my opinion, definition of point-in-time is a bit fuzzy a well. If you are
talking about the timestamps snapshot the way I currently understand this there
are no gurantees between regionservers so the timestamp snapshot is 'not really
a snapshot' either because causality could potentially be violated. (the
limitation in the second paragraph of the description above).
An improvement on copy table is a good improvement and I'm fine with calling
this a fuzzy snapshot or describing it as such in the docs. I'm hesitant to go
and change all the names or add add new commands (fuzzy_snapshot command seems
like overkill). I've filed docs jiras HBASE-7409, HBASE-7410 to put
explanations there and marked them as blockers.
Good enough?
I don't plan on working through the other flavors until we have this, likely
the simplest online snapshot, and all its tooling and plumbing robust and
resolved.
> Simple Flush Snapshot
> ---------------------
>
> Key: HBASE-7321
> URL: https://issues.apache.org/jira/browse/HBASE-7321
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-7321.v2.patch, pre-hbase-7321.v2.patch
>
>
> This snapshot style just issues a region flush and then "snapshots" the
> region.
> This is a simple implementation that gives the equivalent of copytable
> consistency. While by most definitions of consistency if a client writes A
> and then write B to different region servers, only neither, only A, or both
> A+B writes should be present, this one allows the only B case.
--
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
