Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06A6310E60 for ; Fri, 16 Jan 2015 21:21:33 +0000 (UTC) Received: (qmail 65247 invoked by uid 500); 16 Jan 2015 21:21:34 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 65194 invoked by uid 500); 16 Jan 2015 21:21:34 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 65183 invoked by uid 99); 16 Jan 2015 21:21:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jan 2015 21:21:34 +0000 Date: Fri, 16 Jan 2015 21:21:34 +0000 (UTC) From: "Dima Spivak (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)