[
https://issues.apache.org/jira/browse/HBASE-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622550#comment-13622550
]
Jerry He commented on HBASE-7848:
---------------------------------
Hi, Ted, Jonathan
bq. My initial thought was that we take the write lock when we essentially want
to exclusively modify meta (split, move, create, enable/disable),
This is probably a general question on snapshot and specific to this TableLock.
During snapshot, with this TableLock, do we block writes/puts going into the
table/memstore?
or it is done thru other mechanism?
> Use ZK-based read/write lock to make flush-type snapshot robust against table
> enable/disable/alter
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-7848
> URL: https://issues.apache.org/jira/browse/HBASE-7848
> Project: HBase
> Issue Type: Improvement
> Components: snapshots
> Affects Versions: 0.96.0
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 0.95.0, 0.98.0
>
> Attachments: 7848-v1.txt, 7848-v2.txt, hbase-7848_v2.patch,
> hbase-7848_v3.patch
>
>
> Current region split following flush would fail snapshot.
> We can utilize ZK-based read/write lock to make flush-type snapshot robust
--
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
