[
https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634077#comment-14634077
]
Enis Soztutar commented on HBASE-11276:
---------------------------------------
bq. The table/cf is truly optional, but there would be a default value for them
in the tool
Not necessarily. Not all monkeys do table actions. For example
{{serverKillingMonkey}}. That is why having the table optional is important. In
case monkey does not use a table, it is fine to pass null or some non-existing
table.
bq. IMHO, if we require user to make sure the testing table/cf already exists
before running monkeys, then table/cf shouldn't be optional, or if we keep it
as is, we will need the createSchema method to create the table when it doesn't
exist.
What is the point of creating an empty table and doing operations on them from
CM? CM runner should just assume the table will be created from the
concurrently running test. It is fine if table does not exists since CM will
fail the table action, but it will not affect correctness.
> Add back support for running ChaosMonkey as standalone tool
> -----------------------------------------------------------
>
> Key: HBASE-11276
> URL: https://issues.apache.org/jira/browse/HBASE-11276
> Project: HBase
> Issue Type: Task
> Affects Versions: 0.98.0, 0.96.0, 0.99.0
> Reporter: Dima Spivak
> Assignee: Yu Li
> Priority: Minor
> Attachments: HBASE-11276.patch, HBASE-11276_v2.patch,
> HBASE-11276_v3.patch
>
>
> [According to the ref
> guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it
> was once possible to run ChaosMonkey as a standalone tool against a deployed
> cluster. After 0.94, this is no longer possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
