hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16574) Add backup / restore feature to refguide
Date Sat, 11 Nov 2017 22:58:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248716#comment-16248716

stack commented on HBASE-16574:

Did these get addressed?

Nit: On usage, the backupid exists nowhere in the system except as output from the backup
command? Later it is explained what it is which is helpful. Also, later again it is explained
that it does live as part of the backup history. Could be good to call out these facts earlier.

Could also say how long a backup is going to take roughly. Me as an operator would be afraid
to run a backup because I'd think the command could run for ever on my 100 node cluster. Reading
later in the manual, it seems that it could start and return immediately and then I check
in on status. Would be good to surface some of that up here at start of doc. to allay the
fears of the poor operator.

> Add backup / restore feature to refguide
> ----------------------------------------
>                 Key: HBASE-16574
>                 URL: https://issues.apache.org/jira/browse/HBASE-16574
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Frank Welsch
>              Labels: backup
>             Fix For: 2.0.0-beta-1
>         Attachments: B&R command-line tools and configuration (updated).pdf, Backup-and-Restore-Apache_19Sep2016.pdf,
HBASE-16574.001.patch, HBASE-16574.002.patch, HBASE-16574.003.branch-2.patch, hbase-book-16574.003.pdf,
> This issue is to add backup / restore feature description to hbase refguide.
> The description should cover:
> scenarios where backup / restore is used
> backup / restore commands and sample usage
> considerations in setup

This message was sent by Atlassian JIRA

View raw message