You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/07/22 19:26:20 UTC
[jira] [Commented] (HBASE-15227) HBase Backup Phase 3: Fault
tolerance (client/server) support
[ https://issues.apache.org/jira/browse/HBASE-15227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390076#comment-15390076 ]
Ted Yu commented on HBASE-15227:
--------------------------------
Can the recovery be done server side ?
{code}
221 try{
222 admin.disableTable(sysTable);
223 admin.snapshot(snapshot, sysTable);
224 admin.enableTable(sysTable);
225 backupId = admin.backupTables(userRequest);
226 return backupId;
227 } catch (IOException e){
{code}
In the catch block, we don't know which step in the try block fails.
You can use a flag to record last successful step.
But I think recovery on server side makes more sense.
> HBase Backup Phase 3: Fault tolerance (client/server) support
> -------------------------------------------------------------
>
> Key: HBASE-15227
> URL: https://issues.apache.org/jira/browse/HBASE-15227
> Project: HBase
> Issue Type: Task
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBASE-15277-v1.patch
>
>
> System must be tolerant to faults. Backup operations MUST be atomic (no partial completion state in system table)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)