You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Artem Ervits <ar...@nyp.org> on 2013/11/04 23:32:51 UTC

upgrade Ambari-provisioned HBase cluster

Hello all,

My current cluster is

Ambari 1.2.5
HBase 0.94.5.3
Hadoop 1.1.2

I'd like to upgrade HBase to 0.94.12, what are some of the approaches that I can follow to do that?


1.       Wait for next stack release (maybe a problem because we're not ready to go with Hadoop 2)

2.       Compile my own rpms and deploy

Can anyone suggest a good approach that won't break compatibility with future Ambari release?

Same applies to Hadoop, if I wanted to upgrade to 1.2.1

Thank you

Artem Ervits
Artem@nyp.org<ma...@nyp.org>
New York Presbyterian Hospital


This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.

RE: upgrade Ambari-provisioned HBase cluster

Posted by Artem Ervits <ar...@nyp.org>.
My only issue with not upgrading the stack to 1.3.2 is that it doesn't include hbase 0.94.12. Would you advise anything else?

-----Original Message-----
From: Mahadev Konar [mailto:mahadev@hortonworks.com] 
Sent: Tuesday, November 05, 2013 4:23 PM
To: ambari-user@incubator.apache.org
Subject: Re: upgrade Ambari-provisioned HBase cluster

Hi Artem,
  You should check for the compatibility of various hadoop project versions (pig/hive/oozie - others) in the bigtop stack and the ones that you have installed and probably upgrade the full stack. I havent tested with the bits from bigtop stack 0.7 and an upgrade to it - so you might have to try this on a test cluster and validate it.

 Hope that helps.

thanks
mahadev

Mahadev Konar
Hortonworks Inc.
http://hortonworks.com/


On Tue, Nov 5, 2013 at 1:19 PM, Artem Ervits <ar...@nyp.org> wrote:
> I saw that Bigtop 0.7.0 was just released, would I break anything in 
> Ambari
> 1.2.5 if I pulled HBase bits using bigtop repo?
>
>
>
> From: Artem Ervits [mailto:are9004@nyp.org]
> Sent: Tuesday, November 05, 2013 10:12 AM
> To: ambari-user@incubator.apache.org
> Subject: RE: upgrade Ambari-provisioned HBase cluster
>
>
>
> Anyone?
>
>
>
> From: Artem Ervits [mailto:are9004@nyp.org]
> Sent: Monday, November 04, 2013 5:33 PM
> To: ambari-user@incubator.apache.org
> Subject: upgrade Ambari-provisioned HBase cluster
>
>
>
> Hello all,
>
>
>
> My current cluster is
>
>
>
> Ambari 1.2.5
>
> HBase 0.94.5.3
>
> Hadoop 1.1.2
>
>
>
> I'd like to upgrade HBase to 0.94.12, what are some of the approaches 
> that I can follow to do that?
>
>
>
> 1.       Wait for next stack release (maybe a problem because we're not
> ready to go with Hadoop 2)
>
> 2.       Compile my own rpms and deploy
>
>
>
> Can anyone suggest a good approach that won't break compatibility with 
> future Ambari release?
>
>
>
> Same applies to Hadoop, if I wanted to upgrade to 1.2.1
>
>
>
> Thank you
>
>
>
> Artem Ervits
>
> Artem@nyp.org
>
> New York Presbyterian Hospital
>
>
>
>
> This electronic message is intended to be for the use only of the 
> named recipient, and may contain information that is confidential or privileged.
> If you are not the intended recipient, you are hereby notified that 
> any disclosure, copying, distribution or use of the contents of this 
> message is strictly prohibited. If you have received this message in 
> error or are not the named recipient, please notify us immediately by 
> contacting the sender at the electronic mail address noted above, and 
> delete and destroy all copies of this message. Thank you.
>
> ________________________________
>
>
> Confidential Information subject to NYP's (and its affiliates') 
> information management and security policies (http://infonet.nyp.org/QA/HospitalManual).
>
>
> This electronic message is intended to be for the use only of the 
> named recipient, and may contain information that is confidential or privileged.
> If you are not the intended recipient, you are hereby notified that 
> any disclosure, copying, distribution or use of the contents of this 
> message is strictly prohibited. If you have received this message in 
> error or are not the named recipient, please notify us immediately by 
> contacting the sender at the electronic mail address noted above, and 
> delete and destroy all copies of this message. Thank you.
>
> ________________________________
>
>
> Confidential Information subject to NYP's (and its affiliates') 
> information management and security policies (http://infonet.nyp.org/QA/HospitalManual).
>
>
> This electronic message is intended to be for the use only of the 
> named recipient, and may contain information that is confidential or privileged.
> If you are not the intended recipient, you are hereby notified that 
> any disclosure, copying, distribution or use of the contents of this 
> message is strictly prohibited. If you have received this message in 
> error or are not the named recipient, please notify us immediately by 
> contacting the sender at the electronic mail address noted above, and 
> delete and destroy all copies of this message. 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.

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.

Re: upgrade Ambari-provisioned HBase cluster

Posted by Mahadev Konar <ma...@hortonworks.com>.
Hi Artem,
  You should check for the compatibility of various hadoop project
versions (pig/hive/oozie - others) in the bigtop stack and the ones
that you have installed and probably upgrade the full stack. I havent
tested with the bits from bigtop stack 0.7 and an upgrade to it - so
you might have to try this on a test cluster and validate it.

 Hope that helps.

thanks
mahadev

Mahadev Konar
Hortonworks Inc.
http://hortonworks.com/


On Tue, Nov 5, 2013 at 1:19 PM, Artem Ervits <ar...@nyp.org> wrote:
> I saw that Bigtop 0.7.0 was just released, would I break anything in Ambari
> 1.2.5 if I pulled HBase bits using bigtop repo?
>
>
>
> From: Artem Ervits [mailto:are9004@nyp.org]
> Sent: Tuesday, November 05, 2013 10:12 AM
> To: ambari-user@incubator.apache.org
> Subject: RE: upgrade Ambari-provisioned HBase cluster
>
>
>
> Anyone?
>
>
>
> From: Artem Ervits [mailto:are9004@nyp.org]
> Sent: Monday, November 04, 2013 5:33 PM
> To: ambari-user@incubator.apache.org
> Subject: upgrade Ambari-provisioned HBase cluster
>
>
>
> Hello all,
>
>
>
> My current cluster is
>
>
>
> Ambari 1.2.5
>
> HBase 0.94.5.3
>
> Hadoop 1.1.2
>
>
>
> I’d like to upgrade HBase to 0.94.12, what are some of the approaches that I
> can follow to do that?
>
>
>
> 1.       Wait for next stack release (maybe a problem because we’re not
> ready to go with Hadoop 2)
>
> 2.       Compile my own rpms and deploy
>
>
>
> Can anyone suggest a good approach that won’t break compatibility with
> future Ambari release?
>
>
>
> Same applies to Hadoop, if I wanted to upgrade to 1.2.1
>
>
>
> Thank you
>
>
>
> Artem Ervits
>
> Artem@nyp.org
>
> New York Presbyterian Hospital
>
>
>
>
> This electronic message is intended to be for the use only of the named
> recipient, and may contain information that is confidential or privileged.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or use of the contents of this message is
> strictly prohibited. If you have received this message in error or are not
> the named recipient, please notify us immediately by contacting the sender
> at the electronic mail address noted above, and delete and destroy all
> copies of this message. Thank you.
>
> ________________________________
>
>
> Confidential Information subject to NYP's (and its affiliates') information
> management and security policies (http://infonet.nyp.org/QA/HospitalManual).
>
>
> This electronic message is intended to be for the use only of the named
> recipient, and may contain information that is confidential or privileged.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or use of the contents of this message is
> strictly prohibited. If you have received this message in error or are not
> the named recipient, please notify us immediately by contacting the sender
> at the electronic mail address noted above, and delete and destroy all
> copies of this message. Thank you.
>
> ________________________________
>
>
> Confidential Information subject to NYP's (and its affiliates') information
> management and security policies (http://infonet.nyp.org/QA/HospitalManual).
>
>
> This electronic message is intended to be for the use only of the named
> recipient, and may contain information that is confidential or privileged.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or use of the contents of this message is
> strictly prohibited. If you have received this message in error or are not
> the named recipient, please notify us immediately by contacting the sender
> at the electronic mail address noted above, and delete and destroy all
> copies of this message. 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 Ambari-provisioned HBase cluster

Posted by Artem Ervits <ar...@nyp.org>.
I saw that Bigtop 0.7.0 was just released, would I break anything in Ambari 1.2.5 if I pulled HBase bits using bigtop repo?

From: Artem Ervits [mailto:are9004@nyp.org]
Sent: Tuesday, November 05, 2013 10:12 AM
To: ambari-user@incubator.apache.org
Subject: RE: upgrade Ambari-provisioned HBase cluster

Anyone?

From: Artem Ervits [mailto:are9004@nyp.org]<mailto:[mailto:are9004@nyp.org]>
Sent: Monday, November 04, 2013 5:33 PM
To: ambari-user@incubator.apache.org<ma...@incubator.apache.org>
Subject: upgrade Ambari-provisioned HBase cluster

Hello all,

My current cluster is

Ambari 1.2.5
HBase 0.94.5.3
Hadoop 1.1.2

I'd like to upgrade HBase to 0.94.12, what are some of the approaches that I can follow to do that?


1.       Wait for next stack release (maybe a problem because we're not ready to go with Hadoop 2)

2.       Compile my own rpms and deploy

Can anyone suggest a good approach that won't break compatibility with future Ambari release?

Same applies to Hadoop, if I wanted to upgrade to 1.2.1

Thank you

Artem Ervits
Artem@nyp.org<ma...@nyp.org>
New York Presbyterian Hospital


This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
________________________________

Confidential Information subject to NYP's (and its affiliates') information management and security policies (http://infonet.nyp.org/QA/HospitalManual).

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
________________________________

Confidential Information subject to NYP's (and its affiliates') information management and security policies (http://infonet.nyp.org/QA/HospitalManual).

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.

RE: upgrade Ambari-provisioned HBase cluster

Posted by Artem Ervits <ar...@nyp.org>.
Anyone?

From: Artem Ervits [mailto:are9004@nyp.org]
Sent: Monday, November 04, 2013 5:33 PM
To: ambari-user@incubator.apache.org
Subject: upgrade Ambari-provisioned HBase cluster

Hello all,

My current cluster is

Ambari 1.2.5
HBase 0.94.5.3
Hadoop 1.1.2

I'd like to upgrade HBase to 0.94.12, what are some of the approaches that I can follow to do that?


1.       Wait for next stack release (maybe a problem because we're not ready to go with Hadoop 2)

2.       Compile my own rpms and deploy

Can anyone suggest a good approach that won't break compatibility with future Ambari release?

Same applies to Hadoop, if I wanted to upgrade to 1.2.1

Thank you

Artem Ervits
Artem@nyp.org<ma...@nyp.org>
New York Presbyterian Hospital


This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
________________________________

Confidential Information subject to NYP's (and its affiliates') information management and security policies (http://infonet.nyp.org/QA/HospitalManual).

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.