You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Siddharth Wagle <sw...@hortonworks.com> on 2014/02/21 19:16:27 UTC
Re: Error deploying hadoop cluster using Ambari
Correction, /tmp permissions should be "1777".
On Thu, Feb 20, 2014 at 10:20 PM, AKSHATHA SATHYANARAYAN <
akshatha.s@samsung.com> wrote:
>
>
> Hello,
>
>
>
> I am getting the following error while trying to deploy a hadoop cluster
> with 2 data nodes.
>
> err: /Stage[1]/Hdp::Snmp/Hdp::Package[snmp]/Hdp::Package::Process_pkg[snmp]/Hdp::Java::Package[snmp]/Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp]/returns: change from notrun to 0 failed: mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin returned 6 instead of one of [0] at /var/lib/ambari-agent/puppet/modules/hdp/manifests/java/package.pp:49
> notice: /Stage[1]/Hdp::Snmp/Hdp::Package[snmp]/Hdp::Package::Process_pkg[snmp]/Hdp::Java::Package[snmp]/Exec[mkdir -p /usr/jdk64 ; chmod +x /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin; cd /usr/jdk64 ; echo A | /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin -noregister > /dev/null 2>&1 snmp]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snmp/Hdp::Package[snmp]/Hdp::Package::Process_pkg[snmp]/Hdp::Java::Package[snmp]/File[/usr/jdk64/jdk1.6.0_31/bin/java snmp]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snmp/Hdp::Package[snmp]/Hdp::Package::Process_pkg[snmp]/Hdp::Java::Package[snmp]/Anchor[hdp::java::package::snmp::end]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snmp/Hdp::Package[snmp]/Hdp::Package::Process_pkg[snmp]/Anchor[hdp::package::snmp::end]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snmp/Hdp::Snmp-configfile[snmpd.conf]/Hdp::Configfile[/etc/snmp//snmpd.conf]/File[/etc/snmp//snmpd.conf]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snmp/Service[snmpd]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snmp/Exec[snmpd_autostart]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snmp/Anchor[hdp::snmp::end]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[1]/Hdp::Snappy::Package/Hdp::Snappy::Package::Ln[64]/Hdp::Exec[hdp::snappy::package::ln 64]/Exec[hdp::snappy::package::ln 64]/returns: executed successfully
> notice: /Stage[1]/Hdp::Snappy::Package/Hdp::Snappy::Package::Ln[32]/Hdp::Exec[hdp::snappy::package::ln 32]/Exec[hdp::snappy::package::ln 32]/returns: executed successfully
> notice: /Stage[1]/Hdp/Hdp::User[yarn_user]/User[yarn]/ensure: created
> notice: /Stage[1]/Hdp/Hdp::User[hive_user]/User[hive]/ensure: created
> notice: /Stage[1]/Hdp::Create_smoke_user/Hdp::User[smoke_user]/User[ambari-qa]/ensure: created
> notice: /Stage[1]/Hdp::Create_hbase_user/Hdp::User[hbase_user]/User[hbase]/ensure: created
> notice: /Stage[1]/Hdp/Hdp::User[oozie_user]/User[oozie]/ensure: created
> notice: /Stage[1]/Hdp::Create_hbase_user/Hdp::Set_uid[set_hbase_user_uid]/Hdp::Exec[/tmp/changeUid.sh hbase /home/hbase,/tmp/hbase,/usr/bin/hbase 2>/dev/null]/Exec[/tmp/changeUid.sh hbase /home/hbase,/tmp/hbase,/usr/bin/hbase 2>/dev/null]/returns: executed successfully
> notice: /Stage[1]/Hdp/Hdp::User[webhcat_user]/User[hcat]/ensure: created
> notice: /Stage[1]/Hdp::Create_smoke_user/Hdp::Set_uid[set_smoke_user_uid]/Hdp::Exec[/tmp/changeUid.sh ambari-qa /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa 2>/dev/null]/Exec[/tmp/changeUid.sh ambari-qa /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa 2>/dev/null]/returns: executed successfully
> notice: /Stage[2]/Hdp-ganglia/Anchor[hdp-ganglia::begin]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
> notice: /Stage[2]/Hdp-ganglia/Hdp::Group[gmetad_group]/Group[gmetad_group]: Dependency Exec[mkdir -p /tmp/HDP-artifacts/ ; curl -kf --retry 10 http://host-ambari.uisp-hadoop.com:8080/resources//jdk-6u31-linux-x64.bin -o /tmp/HDP-artifacts//jdk-6u31-linux-x64.bin snmp] has failures: true
>
> Getting this same error for Ganglia Monitor Install and DataNode Install.
> Kindly help.
>
>
>
> Thanks,
>
> Akshata
>
>
>
>
>
--
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.
Re: REST api question
Posted by Aaron Cody <ac...@hexiscyber.com>.
thanks Sid - that worked
From: Siddharth Wagle <sw...@hortonworks.com>
Reply-To: <us...@ambari.apache.org>
Date: Wed, 26 Feb 2014 16:48:04 -0800
To: <us...@ambari.apache.org>
Subject: Re: REST api question
Hi Aaron,
You should be able to do this by changing state of a Service component.
Sample API call:
curl -H "X-Requested-By:ambari" -u admin:admin -i -X PUT -d
'{"RequestInfo":{"context":"Stop all datanodes"},"ServiceComponentInfo":
{"state": "INSTALLED"}}'
http://localhost:8080/api/v1/clusters/c1/services/HDFS/components/DATANODE
-Sid
On Wed, Feb 26, 2014 at 4:44 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
> but that¹s to stop the component on a specific host I want to stop all of
> them throughout the cluster.
>
>
> From: Sumit Mohanty <sm...@hortonworks.com>
> Reply-To: <us...@ambari.apache.org>
> Date: Wed, 26 Feb 2014 16:40:39 -0800
> To: "user@ambari.apache.org" <us...@ambari.apache.org>
> Subject: Re: REST api question
>
> You need to use this API to stop the component. The reason its different is
> that stop of the host component is a processed on the host component resource.
>
> curl -u admin:admin -X PUT -d '{"RequestInfo":{"context":"Stop
> Component"},"Body":{"HostRoles":{"state":"INSTALLED"}}}'
> http://AMBARI_SERVER_HOST:8080/api/v1/clusters/c1/hosts/HOSTNAME/host_componen
> ts/COMPONENT_NAME
>
> You can use the wiki to get sample API calls -
> https://cwiki.apache.org/confluence/display/AMBARI/API+usage+scenarios%2C+trou
> bleshooting%2C+and+other+FAQs
>
>
> On Wed, Feb 26, 2014 at 4:30 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
>> we can stop an entire service like so:
>>
>> curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
>> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS
>>
>> but how can I stop all instances of a running component? I had hoped with
>> something like :
>>
>> curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
>> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS/components
>> /DATANODE
>>
>> but this throws an invalid property exception
>>
>> is my URL wrong or are we not allowed to do this sort of thing?
>>
>
>
> 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.
Re: REST api question
Posted by Siddharth Wagle <sw...@hortonworks.com>.
Hi Aaron,
You should be able to do this by changing state of a Service component.
Sample API call:
curl -H "X-Requested-By:ambari" -u admin:admin -i -X PUT -d
'{"RequestInfo":{"context":"Stop all datanodes"},"ServiceComponentInfo":
{"state": "INSTALLED"}}'
http://localhost:8080/api/v1/clusters/c1/services/HDFS/components/DATANODE
-Sid
On Wed, Feb 26, 2014 at 4:44 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
> but that's to stop the component on a specific host... I want to stop all of
> them throughout the cluster....
>
>
> From: Sumit Mohanty <sm...@hortonworks.com>
> Reply-To: <us...@ambari.apache.org>
> Date: Wed, 26 Feb 2014 16:40:39 -0800
> To: "user@ambari.apache.org" <us...@ambari.apache.org>
> Subject: Re: REST api question
>
> You need to use this API to stop the component. The reason its different
> is that stop of the host component is a processed on the host component
> resource.
>
> curl -u admin:admin -X PUT -d '{"RequestInfo":{"context":"Stop
> Component"},"Body":{"HostRoles":{"state":"INSTALLED"}}}' http:
> //AMBARI_SERVER_HOST:8080/api/v1/clusters/c1/hosts/HOSTNAME/host_components/COMPONENT_NAME
>
> You can use the wiki to get sample API calls -
> https://cwiki.apache.org/confluence/display/AMBARI/API+usage+scenarios%2C+troubleshooting%2C+and+other+FAQs
>
>
> On Wed, Feb 26, 2014 at 4:30 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
>
>> we can stop an entire service like so:
>>
>> curl --user admin:admin -i -X PUT -d
>> '{"ServiceInfo":{"state":"INSTALLED"}}'
>> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS
>>
>> but how can I stop all instances of a running component? I had hoped with
>> something like :
>>
>> curl --user admin:admin -i -X PUT -d
>> '{"ServiceInfo":{"state":"INSTALLED"}}'
>> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS/components/DATANODE
>>
>> but this throws an invalid property exception
>>
>> is my URL wrong or are we not allowed to do this sort of thing?
>>
>>
>
> 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.
Re: REST api question
Posted by Aaron Cody <ac...@hexiscyber.com>.
you can stop an entire service :
curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS
so why can¹t we stop all DATANODEs¹ for example?
From: Aaron Cody <ac...@keywcorp.com>
Date: Wed, 26 Feb 2014 16:42:24 -0800
To: <us...@ambari.apache.org>
Subject: Re: REST api question
but that¹s to stop the component on a specific host I want to stop all of
them throughout the cluster.
From: Sumit Mohanty <sm...@hortonworks.com>
Reply-To: <us...@ambari.apache.org>
Date: Wed, 26 Feb 2014 16:40:39 -0800
To: "user@ambari.apache.org" <us...@ambari.apache.org>
Subject: Re: REST api question
You need to use this API to stop the component. The reason its different is
that stop of the host component is a processed on the host component
resource.
curl -u admin:admin -X PUT -d '{"RequestInfo":{"context":"Stop
Component"},"Body":{"HostRoles":{"state":"INSTALLED"}}}'
http://AMBARI_SERVER_HOST:8080/api/v1/clusters/c1/hosts/HOSTNAME/host_compon
ents/COMPONENT_NAME
You can use the wiki to get sample API calls -
https://cwiki.apache.org/confluence/display/AMBARI/API+usage+scenarios%2C+tr
oubleshooting%2C+and+other+FAQs
On Wed, Feb 26, 2014 at 4:30 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
> we can stop an entire service like so:
>
> curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS
>
> but how can I stop all instances of a running component? I had hoped with
> something like :
>
> curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS/components/
> DATANODE
>
> but this throws an invalid property exception
>
> is my URL wrong or are we not allowed to do this sort of thing?
>
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.
Re: REST api question
Posted by Aaron Cody <ac...@hexiscyber.com>.
but that¹s to stop the component on a specific host I want to stop all of
them throughout the cluster.
From: Sumit Mohanty <sm...@hortonworks.com>
Reply-To: <us...@ambari.apache.org>
Date: Wed, 26 Feb 2014 16:40:39 -0800
To: "user@ambari.apache.org" <us...@ambari.apache.org>
Subject: Re: REST api question
You need to use this API to stop the component. The reason its different is
that stop of the host component is a processed on the host component
resource.
curl -u admin:admin -X PUT -d '{"RequestInfo":{"context":"Stop
Component"},"Body":{"HostRoles":{"state":"INSTALLED"}}}'
http://AMBARI_SERVER_HOST:8080/api/v1/clusters/c1/hosts/HOSTNAME/host_compon
ents/COMPONENT_NAME
You can use the wiki to get sample API calls -
https://cwiki.apache.org/confluence/display/AMBARI/API+usage+scenarios%2C+tr
oubleshooting%2C+and+other+FAQs
On Wed, Feb 26, 2014 at 4:30 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
> we can stop an entire service like so:
>
> curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS
>
> but how can I stop all instances of a running component? I had hoped with
> something like :
>
> curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS/components/
> DATANODE
>
> but this throws an invalid property exception
>
> is my URL wrong or are we not allowed to do this sort of thing?
>
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.
Re: REST api question
Posted by Sumit Mohanty <sm...@hortonworks.com>.
You need to use this API to stop the component. The reason its different is
that stop of the host component is a processed on the host component
resource.
curl -u admin:admin -X PUT -d '{"RequestInfo":{"context":"Stop
Component"},"Body":{"HostRoles":{"state":"INSTALLED"}}}' http:
//AMBARI_SERVER_HOST:8080/api/v1/clusters/c1/hosts/HOSTNAME/host_components/COMPONENT_NAME
You can use the wiki to get sample API calls -
https://cwiki.apache.org/confluence/display/AMBARI/API+usage+scenarios%2C+troubleshooting%2C+and+other+FAQs
On Wed, Feb 26, 2014 at 4:30 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
> we can stop an entire service like so:
>
> curl --user admin:admin -i -X PUT -d
> '{"ServiceInfo":{"state":"INSTALLED"}}'
> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS
>
> but how can I stop all instances of a running component? I had hoped with
> something like :
>
> curl --user admin:admin -i -X PUT -d
> '{"ServiceInfo":{"state":"INSTALLED"}}'
> http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS/components/DATANODE
>
> but this throws an invalid property exception
>
> is my URL wrong or are we not allowed to do this sort of thing?
>
>
--
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.
REST api question
Posted by Aaron Cody <ac...@hexiscyber.com>.
we can stop an entire service like so:
curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS
but how can I stop all instances of a running component? I had hoped with
something like :
curl --user admin:admin -i -X PUT -d '{"ServiceInfo":{"state":"INSTALLED"}}'
http://ambari-master.foo.com:8080/api/v1/clusters/c1/services/HDFS/component
s/DATANODE
but this throws an invalid property exception
is my URL wrong or are we not allowed to do this sort of thing?
Re: UPGRADE
Posted by Aaron Cody <ac...@hexiscyber.com>.
thanks Sumit
From: Sumit Mohanty <sm...@hortonworks.com>
Reply-To: <us...@ambari.apache.org>
Date: Wed, 26 Feb 2014 00:26:59 -0800
To: <us...@ambari.apache.org>
Subject: Re: UPGRADE
https://issues.apache.org/jira/browse/AMBARI-1425 has the overall design and
all related JIRAs. A number of the commits have since been removed or
commented out as the feature was never used/regression tested.
In any case, we should apply a fresh perspective and focus on upgrades of
the latest stack releases and beyond. Lets open a new JIRA (let me know if
you want to do it) and discuss the design and implementation requirements.
-Sumit
On Tue, Feb 25, 2014 at 12:36 PM, Sumit Mohanty <sm...@hortonworks.com>
wrote:
> We have not thought of that yet. Some of the current design will remain but
> Ambari has support for custom command/action as well as declarative
> application specification now. That allows for some more tools to use during
> upgrade. So we will definitely try to take advantage of that.
>
> Let me dig up the JIRAs with the details and share them.
>
> -Sumit
>
>
> On Tue, Feb 25, 2014 at 12:26 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
>> Will you be finishing the existing implementation or going in a different
>> direction? Can you share any preliminary design docs?
>> thanks
>>
>> From: Sumit Mohanty <sm...@hortonworks.com>
>> Reply-To: <us...@ambari.apache.org>
>> Date: Tue, 25 Feb 2014 12:03:18 -0800
>>
>> To: <us...@ambari.apache.org>
>> Subject: Re: UPGRADE
>>
>> We do plan to support automatic upgrade as a feature. At this point, this
>> effort is not scheduled for any specific release yet.
>>
>> -Sumit
>>
>>
>> On Tue, Feb 25, 2014 at 11:41 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
>>> ok thanks Sumit - is this a feature you plan to finish or is it now
>>> abandoned for the manual' method?
>>>
>>> From: Sumit Mohanty <sm...@hortonworks.com>
>>> Reply-To: <us...@ambari.apache.org>
>>> Date: Tue, 25 Feb 2014 11:26:41 -0800
>>> To: <us...@ambari.apache.org>
>>> Subject: Re: UPGRADE
>>>
>>> Hi Aaron,
>>>
>>> Ambari does not support automatic upgrade of the stack yet. What you see are
>>> remnants of the feature that we started working on but it is not complete.
>>>
>>> Upgrade, for now, is manual and there are documented steps on how to do it.
>>>
>>> -Sumit
>>>
>>>
>>> On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
>>>> Hello
>>>> I¹m trying to figure out how upgrade works in Ambari I see there is an
>>>> UPGRADE role and various upgrade states in the state machine, but so far I
>>>> haven¹t spotted any information as to how it is supposed to work .. (i¹m
>>>> using 1.2.4) .. is it a work in progress?
>>>> - how do you upgrade from the GUI?
>>>> - how do you upgrade from the REST api?
>>>>
>>>> thanks
>>>>
>>>
>>>
>>> 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.
Re: UPGRADE
Posted by Sumit Mohanty <sm...@hortonworks.com>.
https://issues.apache.org/jira/browse/AMBARI-1425 has the overall design
and all related JIRAs. A number of the commits have since been removed or
commented out as the feature was never used/regression tested.
In any case, we should apply a fresh perspective and focus on upgrades of
the latest stack releases and beyond. Lets open a new JIRA (let me know if
you want to do it) and discuss the design and implementation requirements.
-Sumit
On Tue, Feb 25, 2014 at 12:36 PM, Sumit Mohanty <sm...@hortonworks.com>wrote:
> We have not thought of that yet. Some of the current design will remain
> but Ambari has support for custom command/action as well as declarative
> application specification now. That allows for some more tools to use
> during upgrade. So we will definitely try to take advantage of that.
>
> Let me dig up the JIRAs with the details and share them.
>
> -Sumit
>
>
> On Tue, Feb 25, 2014 at 12:26 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
>
>> Will you be finishing the existing implementation or going in a different
>> direction? Can you share any preliminary design docs?
>> thanks
>>
>> From: Sumit Mohanty <sm...@hortonworks.com>
>> Reply-To: <us...@ambari.apache.org>
>> Date: Tue, 25 Feb 2014 12:03:18 -0800
>>
>> To: <us...@ambari.apache.org>
>> Subject: Re: UPGRADE
>>
>> We do plan to support automatic upgrade as a feature. At this point, this
>> effort is not scheduled for any specific release yet.
>>
>> -Sumit
>>
>>
>> On Tue, Feb 25, 2014 at 11:41 AM, Aaron Cody <ac...@hexiscyber.com>wrote:
>>
>>> ok thanks Sumit - is this a feature you plan to finish or is it now
>>> abandoned for the 'manual' method?
>>>
>>> From: Sumit Mohanty <sm...@hortonworks.com>
>>> Reply-To: <us...@ambari.apache.org>
>>> Date: Tue, 25 Feb 2014 11:26:41 -0800
>>> To: <us...@ambari.apache.org>
>>> Subject: Re: UPGRADE
>>>
>>> Hi Aaron,
>>>
>>> Ambari does not support automatic upgrade of the stack yet. What you see
>>> are remnants of the feature that we started working on but it is not
>>> complete.
>>>
>>> Upgrade, for now, is manual and there are documented steps on how to do
>>> it.
>>>
>>> -Sumit
>>>
>>>
>>> On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <ac...@hexiscyber.com>wrote:
>>>
>>>> Hello
>>>> I'm trying to figure out how upgrade works in Ambari ... I see there is
>>>> an UPGRADE role and various upgrade states in the state machine, but so far
>>>> I haven't spotted any information as to how it is supposed to work .. (i'm
>>>> using 1.2.4) .. is it a work in progress?
>>>> - how do you upgrade from the GUI?
>>>> - how do you upgrade from the REST api?
>>>>
>>>> thanks
>>>>
>>>>
>>>
>>> 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.
Re: UPGRADE
Posted by Sumit Mohanty <sm...@hortonworks.com>.
We have not thought of that yet. Some of the current design will remain but
Ambari has support for custom command/action as well as declarative
application specification now. That allows for some more tools to use
during upgrade. So we will definitely try to take advantage of that.
Let me dig up the JIRAs with the details and share them.
-Sumit
On Tue, Feb 25, 2014 at 12:26 PM, Aaron Cody <ac...@hexiscyber.com> wrote:
> Will you be finishing the existing implementation or going in a different
> direction? Can you share any preliminary design docs?
> thanks
>
> From: Sumit Mohanty <sm...@hortonworks.com>
> Reply-To: <us...@ambari.apache.org>
> Date: Tue, 25 Feb 2014 12:03:18 -0800
>
> To: <us...@ambari.apache.org>
> Subject: Re: UPGRADE
>
> We do plan to support automatic upgrade as a feature. At this point, this
> effort is not scheduled for any specific release yet.
>
> -Sumit
>
>
> On Tue, Feb 25, 2014 at 11:41 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
>
>> ok thanks Sumit - is this a feature you plan to finish or is it now
>> abandoned for the 'manual' method?
>>
>> From: Sumit Mohanty <sm...@hortonworks.com>
>> Reply-To: <us...@ambari.apache.org>
>> Date: Tue, 25 Feb 2014 11:26:41 -0800
>> To: <us...@ambari.apache.org>
>> Subject: Re: UPGRADE
>>
>> Hi Aaron,
>>
>> Ambari does not support automatic upgrade of the stack yet. What you see
>> are remnants of the feature that we started working on but it is not
>> complete.
>>
>> Upgrade, for now, is manual and there are documented steps on how to do
>> it.
>>
>> -Sumit
>>
>>
>> On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <ac...@hexiscyber.com>wrote:
>>
>>> Hello
>>> I'm trying to figure out how upgrade works in Ambari ... I see there is an
>>> UPGRADE role and various upgrade states in the state machine, but so far I
>>> haven't spotted any information as to how it is supposed to work .. (i'm
>>> using 1.2.4) .. is it a work in progress?
>>> - how do you upgrade from the GUI?
>>> - how do you upgrade from the REST api?
>>>
>>> thanks
>>>
>>>
>>
>> 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.
Re: UPGRADE
Posted by Aaron Cody <ac...@hexiscyber.com>.
Will you be finishing the existing implementation or going in a different
direction? Can you share any preliminary design docs?
thanks
From: Sumit Mohanty <sm...@hortonworks.com>
Reply-To: <us...@ambari.apache.org>
Date: Tue, 25 Feb 2014 12:03:18 -0800
To: <us...@ambari.apache.org>
Subject: Re: UPGRADE
We do plan to support automatic upgrade as a feature. At this point, this
effort is not scheduled for any specific release yet.
-Sumit
On Tue, Feb 25, 2014 at 11:41 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
> ok thanks Sumit - is this a feature you plan to finish or is it now abandoned
> for the manual' method?
>
> From: Sumit Mohanty <sm...@hortonworks.com>
> Reply-To: <us...@ambari.apache.org>
> Date: Tue, 25 Feb 2014 11:26:41 -0800
> To: <us...@ambari.apache.org>
> Subject: Re: UPGRADE
>
> Hi Aaron,
>
> Ambari does not support automatic upgrade of the stack yet. What you see are
> remnants of the feature that we started working on but it is not complete.
>
> Upgrade, for now, is manual and there are documented steps on how to do it.
>
> -Sumit
>
>
> On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
>> Hello
>> I¹m trying to figure out how upgrade works in Ambari I see there is an
>> UPGRADE role and various upgrade states in the state machine, but so far I
>> haven¹t spotted any information as to how it is supposed to work .. (i¹m
>> using 1.2.4) .. is it a work in progress?
>> - how do you upgrade from the GUI?
>> - how do you upgrade from the REST api?
>>
>> thanks
>>
>
>
> 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.
Re: UPGRADE
Posted by Sumit Mohanty <sm...@hortonworks.com>.
We do plan to support automatic upgrade as a feature. At this point, this
effort is not scheduled for any specific release yet.
-Sumit
On Tue, Feb 25, 2014 at 11:41 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
> ok thanks Sumit - is this a feature you plan to finish or is it now
> abandoned for the 'manual' method?
>
> From: Sumit Mohanty <sm...@hortonworks.com>
> Reply-To: <us...@ambari.apache.org>
> Date: Tue, 25 Feb 2014 11:26:41 -0800
> To: <us...@ambari.apache.org>
> Subject: Re: UPGRADE
>
> Hi Aaron,
>
> Ambari does not support automatic upgrade of the stack yet. What you see
> are remnants of the feature that we started working on but it is not
> complete.
>
> Upgrade, for now, is manual and there are documented steps on how to do it.
>
> -Sumit
>
>
> On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
>
>> Hello
>> I'm trying to figure out how upgrade works in Ambari ... I see there is an
>> UPGRADE role and various upgrade states in the state machine, but so far I
>> haven't spotted any information as to how it is supposed to work .. (i'm
>> using 1.2.4) .. is it a work in progress?
>> - how do you upgrade from the GUI?
>> - how do you upgrade from the REST api?
>>
>> thanks
>>
>>
>
> 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.
Re: UPGRADE
Posted by Aaron Cody <ac...@hexiscyber.com>.
ok thanks Sumit - is this a feature you plan to finish or is it now
abandoned for the manual' method?
From: Sumit Mohanty <sm...@hortonworks.com>
Reply-To: <us...@ambari.apache.org>
Date: Tue, 25 Feb 2014 11:26:41 -0800
To: <us...@ambari.apache.org>
Subject: Re: UPGRADE
Hi Aaron,
Ambari does not support automatic upgrade of the stack yet. What you see are
remnants of the feature that we started working on but it is not complete.
Upgrade, for now, is manual and there are documented steps on how to do it.
-Sumit
On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
> Hello
> I¹m trying to figure out how upgrade works in Ambari I see there is an
> UPGRADE role and various upgrade states in the state machine, but so far I
> haven¹t spotted any information as to how it is supposed to work .. (i¹m using
> 1.2.4) .. is it a work in progress?
> - how do you upgrade from the GUI?
> - how do you upgrade from the REST api?
>
> thanks
>
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.
Re: UPGRADE
Posted by Sumit Mohanty <sm...@hortonworks.com>.
Hi Aaron,
Ambari does not support automatic upgrade of the stack yet. What you see
are remnants of the feature that we started working on but it is not
complete.
Upgrade, for now, is manual and there are documented steps on how to do it.
-Sumit
On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <ac...@hexiscyber.com> wrote:
> Hello
> I'm trying to figure out how upgrade works in Ambari ... I see there is an
> UPGRADE role and various upgrade states in the state machine, but so far I
> haven't spotted any information as to how it is supposed to work .. (i'm
> using 1.2.4) .. is it a work in progress?
> - how do you upgrade from the GUI?
> - how do you upgrade from the REST api?
>
> thanks
>
>
--
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.
UPGRADE
Posted by Aaron Cody <ac...@hexiscyber.com>.
Hello
I¹m trying to figure out how upgrade works in Ambari I see there is an
UPGRADE role and various upgrade states in the state machine, but so far I
haven¹t spotted any information as to how it is supposed to work .. (i¹m
using 1.2.4) .. is it a work in progress?
- how do you upgrade from the GUI?
- how do you upgrade from the REST api?
thanks