[
https://issues.apache.org/jira/browse/HBASE-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412027#comment-16412027
]
Josh Elser commented on HBASE-19258:
------------------------------------
{quote}The main issues here are timeout: what timeout should we set, taking
into account that all numbers are configurable. You can set 1K rows or 1B rows
to load, for example. Another one is how to catch that waiting was over due to
timeout expiration? This complicates simple stuff a lot
{quote}
A common practice is to just set an upper-bound on run-time. Since the duration
of the test is user-defined, we could poll inside of this test to limit a
maximum run time.
However, since this is something that can be externally automated, I think
improving that later is fine.
+1 I'm ok with v2 as it is.
[[email protected]], [~mdrob], do you have more feedback?
> IntegrationTest for Backup and Restore
> --------------------------------------
>
> Key: HBASE-19258
> URL: https://issues.apache.org/jira/browse/HBASE-19258
> Project: HBase
> Issue Type: Test
> Components: integration tests
> Reporter: Josh Elser
> Assignee: Vladimir Rodionov
> Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HBASE-19258.v1.patch, HBASE-19258.v2.patch
>
>
> See chatter at https://docs.google.com/document/d/1xbPlLKjOcPq2LDqjbSkF6uND
> AG0mzgOxek6P3POLeMc/edit?usp=sharing
> We need to get an IntegrationTest in place for backup and restore.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)