[
https://issues.apache.org/jira/browse/HBASE-17614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137572#comment-16137572
]
Josh Elser commented on HBASE-17614:
------------------------------------
{noformat}
Running org.apache.hadoop.hbase.backup.master.TestBackupLogCleaner
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 83.801 sec - in
org.apache.hadoop.hbase.backup.master.TestBackupLogCleaner
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
{noformat}
/me groans. This passed after I added log4j.properties to
hbase-backup/src/test/resources.
[~stack], curious it takes so much longer for you. Busy/slow disk? Something
else?
At this point, I think it would be best to commit (I also see some commented
out stuff in hbase-backup/pom.xml that I would delete before commit) and deal
with problematic tests on the asf infra. Any objections? I'm +1 at this point.
[~mdrob], you all-clear now? Or should I still tread lightly on branch-2 to
avoid smacking you?
> Move Backup/Restore into separate module
> -----------------------------------------
>
> Key: HBASE-17614
> URL: https://issues.apache.org/jira/browse/HBASE-17614
> Project: HBase
> Issue Type: Task
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Blocker
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBASE-17614-v1.patch, HBASE-17614-v2.patch,
> HBASE-17614-v3.patch, HBASE-17614-v4.patch
>
>
> Move all the backup code into separate hbase-backup module.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
