hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dima Spivak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12869) Add a ClouderaManager implementation of the ClusterManager interface
Date Fri, 16 Jan 2015 21:21:34 GMT

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

Dima Spivak commented on HBASE-12869:
-------------------------------------

The trouble is Cloudera Manager (just like Ambari) has a [Java API|http://cloudera.github.io/cm_api/docs/java-client/]
to use, so it's not just a matter of changing start script locations. As I said, I'm fine
keeping it out of the project, but it just means more hurdles to people using hbase-it.

> Add a ClouderaManager implementation of the ClusterManager interface
> --------------------------------------------------------------------
>
>                 Key: HBASE-12869
>                 URL: https://issues.apache.org/jira/browse/HBASE-12869
>             Project: HBase
>          Issue Type: New Feature
>          Components: integration tests
>            Reporter: Dima Spivak
>            Assignee: Dima Spivak
>
> ChaosMonkey doesn't work on HBase/CDH clusters set up using Cloudera Manager because
Cloudera Manager doesn't make use of hbase-daemon.sh (so killed RegionServers can't be started
up again). To fix this, I want to implement ClouderaManagerClusterManager. I could just as
well keep this internal (or only include it in Cloudera's distribution), but seeing as how
it would open up more people across the community to run hbase-it, I'd like to commit it upstream.
Anyone object?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message