hbase-issues mailing list archives

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

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

Andrew Purtell commented on HBASE-12869:

Thanks for doing the investigation [~dimaspivak]. Implementing a single  "RESTApiClusterManager"
that for the time being only works with the Cloudera Manager is fine in my opinion. The project
has asked for and gotten as neutral an implementation as is feasible. RESTApiClusterManager
can be extended at some future time to handle alternate interfaces. For example there could
be nested interfaces like Request and Response that could be implemented for a different API
and configured in.

> 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

View raw message