That's cute, its the df(1) of all my mounts on all my nodes. On the machine I'm trying to set as the namenode, there are 17 mounts, some local, some NFS, and yes, some of those NFS mountpoints are /home/foo.
There are also lots of filesystems, local ones even, empty ones waiting for grate gob's o HDFS metadata, that don't start with /home. Can I override its recommendation somehow? Or is this the point where we just go get the tarballs and do stuff by hand? (Just as an aside, I don't really care about using Ambari to deploy the cluster. I want the monitoring tools. But unfortunately it doesn't seem that Ambari can monitor a cluster that it didn't deploy.) On Jul 31, 2015, at 4:29 PM, Yusaku Sako <[email protected]> wrote: > It seems like this is happening because the default directory recommendations > given contains /home as a mount point. > What is the output of: > > GET /api/v1/clusters/<cluster-name>/hosts?fields=Hosts/disk_info/* > > Yusaku > > From: Ian Soboroff > Reply-To: "[email protected]" > Date: Friday, July 31, 2015 at 1:21 PM > To: "[email protected]" > Subject: Re: Ambari 2.1.0 on HDP 2.3 problem deploying HDFS > > I got frustrated enough that I cleared everything down to a naked Postgres > install, and put everything back step-by-step. I still get this error. I > repeat, I haven't given any values to the NameNode directories config, > because I don't get an opportunity to do. > > Reloading the page or going Back then Next do not solve the problem for me. > > Ian > > On Jul 31, 2015, at 2:44 PM, Srimanth Gunturi <[email protected]> > wrote: > >> Hi Ian, >> I was able to reproduce issue by jumping between other service configs >> *after* setting the value to "/home/foo". >> I have opened https://issues.apache.org/jira/browse/AMBARI-12612 to fix >> this issue. >> >> The workaround is to either hit Back followed by Next. OR just refresh the >> page to get back the original config value. >> Regards, >> Srimanth >> >> >> From: Srimanth Gunturi <[email protected]> >> Sent: Friday, July 31, 2015 11:10 AM >> To: [email protected] >> Subject: Re: Ambari 2.1.0 on HDP 2.3 problem deploying HDFS >> >> Hi Ian, >> Which version of Ambari are you using to install HDP-2.3? >> Can you provide the output of 'ambari-server --hash' command? Also, do you >> see any Javascript exceptions? >> >> I have just attempted to reproduce the issue by adding HDFS service, but do >> not see the issue (screenshot attached). >> If you are not entering any /home value, and Ambari is not providing it by >> default, I am trying to figure out where it is coming from. >> >> <Screen Shot 2015-07-31 at 10.57.13 AM.png> >> >> >> What output do you see when you go to following URL in browser? >> http://[ambari-server]:8080/api/v1/clusters/[cluster-name]/configurations?type=hdfs-site >> - Replace [ambari-server] with your Ambari server hostname >> - Replace [cluster-name] with your cluster ID >> - Make sure you are logged in >> Regards, >> Srimanth >> >> >> From: Ian Soboroff <[email protected]> >> Sent: Friday, July 31, 2015 10:48 AM >> To: [email protected] >> Subject: Re: Ambari 2.1.0 on HDP 2.3 problem deploying HDFS >> >> I haven't set the value of 'NameNode directories' to anything. The >> interface doesn't let me. >> Ian >> >> On Jul 31, 2015, at 1:35 PM, Srimanth Gunturi <[email protected]> >> wrote: >> >>> Hi Ian, >>> Did you set the value of any of the 'NameNode directories' to begin with >>> /home or /homes? >>> We show that error when it does - >>> https://github.com/apache/ambari/blob/trunk/ambari-web/app/utils/validator.js#L96 >>> (screenshot attached) >>> >>> What is strange in your case is that it does not show the text area so that >>> you correct it. >>> Can you detail the exact actions that resulted in this outcome? >>> Alternatively, do you see any Javascript errors in the Javascript console, >>> and have you tried it in other browsers? >>> Regards, >>> Srimanth >>> >>> <Screen Shot 2015-07-31 at 10.27.30 AM.png> >>> >>> From: Ian Soboroff <[email protected]> >>> Sent: Friday, July 31, 2015 8:38 AM >>> To: [email protected] >>> Subject: Ambari 2.1.0 on HDP 2.3 problem deploying HDFS >>> >>> I'm installing HDP 2.3 on a new cluster, and taking it slow. I'm using >>> Ambari to deploy, and so far have only installed Zookeeper and >>> Ambari-metrics. >>> >>> When I go to install HDFS, I get to service customization, and it won't let >>> me set a NameNode directory. I've attached a screenshot. When I hover the >>> mouse over the 'NameNode directories' alert, the mouseover text says "Can't >>> start with home(s)". At this point there is no way to proceed with the >>> installation. >>> >>> Help! >>> >>> Ian >>> >>> <Screen Shot 2015-07-31 at 11.36.33 AM.png> >> >
