Artem,
 That is good to hear. Feel free to file jiras if you find any issues! 

thanks
mahadev

On Jan 15, 2013, at 9:49 AM, Artem Ervits wrote:

> I will certainly do that. Not sure if it is relevant but I was able to 
> successfully install and setup Ganglia monitoring for a single node Hadoop 
> cluster using the Ambari repos from the 1.2.0 documentation. Prior to that, I 
> was having a lot of problems installing Ganglia from epel repo with version 
> 3.1.17, the 3.2.0 version found in HDP repos, works well!
>  
> Thank you.
>  
> From: Mahadev Konar [mailto:[email protected]] 
> Sent: Tuesday, January 15, 2013 11:01 AM
> To: [email protected]
> Subject: Re: ETA: Release 1.2.0
>  
>  Artem,
>  Usually a release takes 10 days or so to go through. You should be able to 
> try out the release from the docs: the rpms and other artifacts are available 
> on the repository links in the docs below: 
>  
> http://incubator.apache.org/ambari/1.2.0/installing-hadoop-using-ambari/content/index.html
>  
>  Please let us know how it goes.
>  
> thanks
> mahadev
>  
> 
> On Tue, Jan 15, 2013 at 7:49 AM, Artem Ervits <[email protected]> wrote:
> Hello all,
>  
> I noticed that documentation on the main site was updated as of yesterday and 
> Jira only has a number of unresolved issues. Is there an ETA on the RC 
> release? I’d love to start testing, is there a link to updated bits or do I 
> need to pull from trunk and compile?
>  
> Thanks.
>  
> Artem Ervits
> Data Analyst
> 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.
>  
> --------------------
>  
> 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.
>  
>  
>  
> --------------------
> 
> 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.
> 
> --------------------
> 
> 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.
> 
> 
> 

Reply via email to