Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E2E4D1080B for ; Wed, 14 Aug 2013 22:56:39 +0000 (UTC) Received: (qmail 1350 invoked by uid 500); 14 Aug 2013 22:56:39 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 1323 invoked by uid 500); 14 Aug 2013 22:56:39 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 1301 invoked by uid 99); 14 Aug 2013 22:56:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Aug 2013 22:56:39 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of smohanty@hortonworks.com designates 209.85.160.49 as permitted sender) Received: from [209.85.160.49] (HELO mail-pb0-f49.google.com) (209.85.160.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Aug 2013 22:56:34 +0000 Received: by mail-pb0-f49.google.com with SMTP id xb4so71138pbc.8 for ; Wed, 14 Aug 2013 15:56:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:in-reply-to:mime-version:content-type; bh=b5HclFidIEWRoyHyH1SZTcHfOoEb/e1TPbukR0RMyOM=; b=mWMCaV6iFCSzEe4pp7DBZ0QNQE2N7hvwKgOIm365a2SllEJ/hKJTK8cnl27YxKcArY RAVgGHEW2/X6pMQZZslfTMeh7sURXpU3up/yOjaG0oGkNaf1JAUmazGnjJ82ZBiBnmEt OBpcXGSJ9aAfeyE8lgFN3TLIuixm2oNFVe9dczPLg/2jfGO7DxFdXuAZYkVwoUyLfo3T PKtC9Zka0PCEz9VlleDXr4oTr4GPN1BdLxF/9AvMGLHOoT1gJIZHLG11BnUQ9XXUp5Rz QLi9SxwIlGrnLwI7ffYe2sBJEI/rG2yNdjFRImGPdDx1lxv6PwmzrGcQpsPrAMy2R7Wu W/0g== X-Gm-Message-State: ALoCoQkUlY/FjisYiqSVnaLhDZQukJ8ZGvmV4O+e1KnwV3qbk74jeoB4ibZRIXwlcAVzYb3OMGsmOSuGYnsssWef7PJjYOpuBy2UiQS5Ti1G6z6DGgycMxM= X-Received: by 10.66.218.166 with SMTP id ph6mr12537352pac.28.1376520974218; Wed, 14 Aug 2013 15:56:14 -0700 (PDT) Received: from [10.11.3.21] ([192.175.27.2]) by mx.google.com with ESMTPSA id qp10sm55952457pab.13.2013.08.14.15.56.11 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 14 Aug 2013 15:56:13 -0700 (PDT) User-Agent: Microsoft-MacOutlook/14.2.5.121010 Date: Wed, 14 Aug 2013 15:56:07 -0700 Subject: Re: HDP Cluster scaling From: Sumit Mohanty To: Message-ID: Thread-Topic: HDP Cluster scaling In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org Unfortunately, host delete feature is not yet available. Likely, availability is after 1.2.5. The expectation is that host can be deleted after the mapped components are deleted. -Sumit On 8/14/13 3:50 PM, "Jon Maron" wrote: >Thanks! > >Follow up question: > >To scale down, do I simply have to leverage the REST API to DELETE the >given host? > >-- Jon > >On Aug 14, 2013, at 5:30 PM, Sumit Mohanty >wrote: > >> 1) Is it the ideal approach? Is there a more direct way of interacting >> with ambari to provision a new host? >> >> The steps you have is the ideal approach. Alternatively, there is >> bootstrap API but it will also require Ambari to have SSH access. Even >> then the number of steps will not be smaller. >> >> 2) I am having an issue with the final step. During the invocation I >> get the following error: >> >> >> You are right. The client components do not transition to STARTED. So >>you >> need to only issue INSTALLED-->STARTED for the non client components. >> >> -Sumit >> >> On 8/14/13 12:57 PM, "Jon Maron" wrote: >> >>> Hi, >>> >>> I'm working on the Savanna HDP plugin, currently working on the >>> capability to scale a cluster (add hosts, remove hosts). The current >>> approach to adding a host is to: >>> >>> 1) Install the ambari agent on the host >>> 2) start the ambari agent >>> 3) register the host >>> 4) add the required host components (based on the node group to which >>> it is being added) >>> 5) install components (transition state from INIT to INSTALLED) >>> 6) start the components (transition state from INSTALLED to STARTED) >>> >>> I have a couple of questions regarding this approach: >>> >>> 1) Is it the ideal approach? Is there a more direct way of >>> interacting with ambari to provision a new host? >>> >>> 2) I am having an issue with the final step. During the invocation I >>> get the following error: >>> >>> >>> >>> >>content="text/html;charset=ISO-8859-1"/> >>> Error 500 Invalid desired state for a client component >>> >>> >>>

HTTP ERROR: 500

>>>

Problem accessing >>> >>>/api/v1/clusters/my-cluster/hosts/my-cluster-slave-003.novalocal/host_co >>>mp >>> onents. Reason: >>>

    Invalid desired state for a client component

>>>
Powered by Jetty:// >>> >>> The mix of components that are in the installed state is: >>> >>> { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal/host_components?HostRoles/state=INSTALLED", >>> "items" : [ >>> { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal/host_components/DATANODE", >>> "HostRoles" : { >>> "cluster_name" : "my-cluster", >>> "component_name" : "DATANODE", >>> "state" : "INSTALLED", >>> "host_name" : "my-cluster-slave-003.novalocal" >>> }, >>> "host" : { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal" >>> } >>> }, >>> { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal/host_components/MAPREDUCE_CLIENT", >>> "HostRoles" : { >>> "cluster_name" : "my-cluster", >>> "component_name" : "MAPREDUCE_CLIENT", >>> "state" : "INSTALLED", >>> "host_name" : "my-cluster-slave-003.novalocal" >>> }, >>> "host" : { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal" >>> } >>> }, >>> { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal/host_components/HDFS_CLIENT", >>> "HostRoles" : { >>> "cluster_name" : "my-cluster", >>> "component_name" : "HDFS_CLIENT", >>> "state" : "INSTALLED", >>> "host_name" : "my-cluster-slave-003.novalocal" >>> }, >>> "host" : { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal" >>> } >>> }, >>> { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal/host_components/GANGLIA_MONITOR", >>> "HostRoles" : { >>> "cluster_name" : "my-cluster", >>> "component_name" : "GANGLIA_MONITOR", >>> "state" : "INSTALLED", >>> "host_name" : "my-cluster-slave-003.novalocal" >>> }, >>> "host" : { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal" >>> } >>> }, >>> { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal/host_components/TASKTRACKER", >>> "HostRoles" : { >>> "cluster_name" : "my-cluster", >>> "component_name" : "TASKTRACKER", >>> "state" : "INSTALLED", >>> "host_name" : "my-cluster-slave-003.novalocal" >>> }, >>> "host" : { >>> "href" : >>> >>>"http://172.18.3.5:8080/api/v1/clusters/my-cluster/hosts/my-cluster-slav >>>e- >>> 003.novalocal" >>> } >>> } >>> ] >>> } >>> >>> So it appears that "CLIENT" components are not transitioned into the >>> STARTED state? Do I need to iterate thru these and avoid starting >>> components with CLIENT in their name? >>> >>> -- Jon >>> -- >>> CONFIDENTIALITY NOTICE >>> NOTICE: This message is intended for the use of the individual or >>>entity >>> to >>> which it is addressed and may contain information that is confidential, >>> privileged and exempt from disclosure under applicable law. If the >>>reader >>> of this message is not the intended recipient, you are hereby notified >>> that >>> any printing, copying, dissemination, distribution, disclosure or >>> forwarding of this communication is strictly prohibited. If you have >>> received this communication in error, please contact the sender >>> immediately >>> and delete it from your system. Thank You. >> >> >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or >>entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the >>reader >> of this message is not the intended recipient, you are hereby notified >>that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender >>immediately >> and delete it from your system. Thank You. > > >-- >CONFIDENTIALITY NOTICE >NOTICE: This message is intended for the use of the individual or entity >to >which it is addressed and may contain information that is confidential, >privileged and exempt from disclosure under applicable law. If the reader >of this message is not the intended recipient, you are hereby notified >that >any printing, copying, dissemination, distribution, disclosure or >forwarding of this communication is strictly prohibited. If you have >received this communication in error, please contact the sender >immediately >and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.