[
https://issues.apache.org/jira/browse/HBASE-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012114#comment-14012114
]
Hadoop QA commented on HBASE-10935:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12647304/hbase-10935.txt
against trunk revision .
ATTACHMENT ID: 12647304
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9634//console
This message is automatically generated.
> support snapshot policy where flush memstore can be skipped to prevent
> production cluster freeze
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-10935
> URL: https://issues.apache.org/jira/browse/HBASE-10935
> Project: HBase
> Issue Type: New Feature
> Components: shell, snapshots
> Affects Versions: 0.94.7, 0.94.18
> Reporter: Tianying Chang
> Assignee: Tianying Chang
> Priority: Minor
> Fix For: 0.99.0
>
> Attachments: hbase-10935.txt, jira-10935-trunk.patch
>
>
> We are using snapshot feature to do HBase disaster recovery. We will do
> snapshot in our production cluster periodically. The current flush snapshot
> policy require all regions of the table to coordinate to prevent write and do
> flush at the same time. Since we use WALPlayer to complete the data that is
> not in the snapshot HFile, we don't need the snapshot to do coordinated
> flush. The snapshot just recored all the HFile that are already there.
> I added the parameter in the HBase shell. So people can choose to use the
> NoFlush snapshot when they need, like below. Otherwise, the default flush
> snpahot support is not impacted.
> >snaphot 'TestTable', 'TestSnapshot', 'skipFlush'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
