Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 15 Jan 2015 22:12:34 +0000 (UTC)
From: "Dima Spivak (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12767861.1421359914000.96314.1421359954537@Atlassian.JIRA>
In-Reply-To: <JIRA.12767861.1421359914000@Atlassian.JIRA>
References: <JIRA.12767861.1421359914000@Atlassian.JIRA>
 <JIRA.12767861.1421359914076@arcas>
Subject: [jira] [Created] (HBASE-12869) Add a ClouderaManager implementation
 of the ClusterManager interface
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Dima Spivak created HBASE-12869:
-----------------------------------

             Summary: 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)