On Mon, Oct 15, 2012 at 1:00 PM, Kartashov, Andy <[email protected]> wrote: > I run Hadoop in pseudo-distrib on amazon instance in the cloud. Shall I > change "localhost" in both core-site and mapred-site to my< my-host-name>?
It depends on the desired behavior, but generally it's easiest if you have the hostnames in *.xml match the hostname of the host in question. Accessing the webUIs can be annoying depending on your browser config, however. > p.s. I can see Namenode status through Web-based interface using url: > http://<my-host-name>:50070 however cannot access JobTracker (MapReduce > master) using : http://<my-host-name>:50030 :( Keep in mind that opening up your EC2 Hadoop cluster to arbitrary HTTP access means that anyone in the world who guesses your IP can access the files you have stored on HDFS. Much better to use a VPN or ssh SOCKS5 port forwarding and keep the Hadoop TCP ports firewalled off using AWS security policies. There are unsavoury people who scan EC2 IP ranges looking for unsecured services like Hadoop, so don't think that "I didn't publish my IP, I am safe" will save you! -andy > > Andy Kartashov > > > -----Original Message----- > From: Andy Isaacson [mailto:[email protected]] > Sent: Monday, October 15, 2012 3:52 PM > To: [email protected] > Subject: Re: Issue when clicking on BrowseFileSystem > > Oh, you've *configured* "localhost" as your hostname in the hadoop *.xml > files. Yes, that'll result in the behavior you're seeing. > > I was assuming you were using a hostname that other machines can resolve. For > example running on my laptop I use "adit420" (which is what the laptop calls > itself). When running on VMs using > kvm+virt-manager, I configure my hostnames to the hostnames of the > VMs, for example vm01.local, vm02.local, et cetera. (The .local > pseudo-domain is managed by avahi.) > > You mustn't delete the localhost line from /etc/hosts as that might cause a > lot of other stuff to fail, possibly including sshd, xorg, Gnome, etc. > > -andy > > On Mon, Oct 15, 2012 at 12:24 PM, Kartashov, Andy <[email protected]> > wrote: >> Andy, >> >> My /etc/hosts does say: 127.0.0.1 localhost.localdomain >> localhost >> Shall I delete this entry? >> >> The only reference to localhost is in: >> >> Core-site: >> <property> >> <name>fs.default.name</name> >> <value>hdfs://localhost:8020</value> >> </property> >> >> Mapred-site >> <property> >> <name>mapred.job.tracker</name> >> <value>localhost:8021</value> >> </property> >> >> Andy Kartashov >> MPAC >> Architecture R&D, Co-op >> 1340 Pickering Parkway, Pickering, L1V 0C4 >> 1 Phone : (905) 837 6269 >> 6 Mobile: (416) 722 1787 >> [email protected] >> >> -----Original Message----- >> From: Andy Isaacson [mailto:[email protected]] >> Sent: Friday, October 12, 2012 6:24 PM >> To: [email protected] >> Subject: Re: Issue when clicking on BrowseFileSystem >> >> On Fri, Oct 12, 2012 at 2:09 PM, Kartashov, Andy <[email protected]> >> wrote: >>> It displays: >>> /browseDirectory.jsp?namenodeInfoPort=50070&dir=/&nnaddr=localhost.lo >>> c >>> aldomain:8020 >> >> OK, there are two clues there that your DN and NN both think of themselves >> as being on localhost -- the http://<datanode> portion of the URL is showing >> the DN address as localhost, and the nnaddr=localhost is showing the NN >> address as localhost. >> >> I'd check your /etc/hosts for your hostname and look at the hdfs-site.xml >> for any occurrences of localhost. >> >> -andy >> >>> >>> >>> Andy Kartashov >>> MPAC >>> Architecture R&D, Co-op >>> 1340 Pickering Parkway, Pickering, L1V 0C4 >>> 1 Phone : (905) 837 6269 >>> 6 Mobile: (416) 722 1787 >>> [email protected] >>> >>> >>> -----Original Message----- >>> From: Andy Isaacson [mailto:[email protected]] >>> Sent: Friday, October 12, 2012 4:31 PM >>> To: [email protected] >>> Subject: Re: Issue when clicking on BrowseFileSystem >>> >>> On Fri, Oct 12, 2012 at 11:42 AM, Kartashov, Andy <[email protected]> >>> wrote: >>>> You are absolutely right. It was inded "localhost..:" in the URL. When >>>> I changed it to my IP address the page duly loaded. Which .xml file is >>>> responsible for this setting? >>> >>> It depends on which URL, you left out that part of the answer. :) When you >>> click the link on dfsHealth.jsp, does the error page have >>> nn_browsedfscontent.jsp in the URL bar, or does it have browseDirectory.jsp >>> in the URL bar? >>> >>> The NN address can be specified with dfs.namenode.http-address and the DN >>> with dfs.datanode.http.address but you shouldn't need to configure those by >>> hand, the code is supposed to be smart enough to figure it out >>> automatically. It works in my Hadoop 2.0.x configurations here, so I'd like >>> to track down what is different about your configuration in case we need to >>> fix the code to DTRT for that kind of configuration. >>> >>> The first thing I would check is to make sure your server name is not >>> listed as 127.0.1.1 in /etc/hosts on the server. Since this (arguably >>> broken) configuration is the default for some distros, it would be nice if >>> Hadoop could handle it automatically, but in my experience things work much >>> better when I delete that line from /etc/hosts. >>> >>> -andy >>> >>>> Cheers, >>>> Andy >>>> >>>> >>>> -----Original Message----- >>>> From: Andy Isaacson [mailto:[email protected]] >>>> Sent: Friday, October 12, 2012 2:10 PM >>>> To: [email protected] >>>> Subject: Re: Issue when clicking on BrowseFileSystem >>>> >>>> Andy, >>>> >>>> It sounds like your namenode thinks the datanode is on localhost. The >>>> "browse the filesystem" URL gets its IP address from the DN registration >>>> message. Is the URL that throws dns_unresolved_hostname the >>>> nn_browsedfscontent.jsp URL, or the browseDirectory.jsp that it redirects >>>> to? >>>> >>>> What's your dfs.namenode.rpc-address and http-address settings? Are there >>>> any odd entries in /etc/hosts like having your hostname listed on a >>>> 127.0.0.1 line? Is this on a single-node cluster or a multi-node cluster? >>>> >>>> If none of the above seems diagnostic, what does the >>>> "NameSystem.registerDatanode: node registration from >>>> DatanodeRegistration(192.168.122.87" log messages in your namenode log >>>> look like? >>>> >>>> -andy >>>> >>>> On Fri, Oct 12, 2012 at 10:20 AM, Kartashov, Andy <[email protected]> >>>> wrote: >>>>> hadoop version >>>>> Hadoop 2.0.0-cdh4.0.1 >>>>> Subversion >>>>> file:///data/1/jenkins/workspace/generic-package-rhel64-6-0/topdir/ >>>>> B U I >>>>> LD/hadoop-2.0.0-cdh4.0.1/src/hadoop-common-project/hadoop-common >>>>> >>>>> Andy Kartashov >>>>> MPAC >>>>> Architecture R&D, Co-op >>>>> 1340 Pickering Parkway, Pickering, L1V 0C4 >>>>> 1 Phone : (905) 837 6269 >>>>> 6 Mobile: (416) 722 1787 >>>>> [email protected] >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: Harsh J [mailto:[email protected]] >>>>> Sent: Friday, October 12, 2012 11:41 AM >>>>> To: [email protected] >>>>> Subject: Re: Issue when clicking on BrowseFileSystem >>>>> >>>>> What versions of Hadoop are you both running? I seem to have it working >>>>> fine on a consistent networking environment setup. >>>>> >>>>> On Fri, Oct 12, 2012 at 6:37 PM, Kartashov, Andy <[email protected]> >>>>> wrote: >>>>>> I do too can open <domain>:50070/dfshealth.jsp page and click NameNode >>>>>> Logs link however when I click on Browse the filesystem link I get the >>>>>> following: >>>>>> >>>>>> Network Error (dns_unresolved_hostname) Your requested host >>>>>> "localhost.localdomain" could not be resolved by DNS. >>>>>> For assistance, contact your network support team. >>>>>> >>>>>> Rgds, >>>>>> Andy >>>>>> >>>>>> -----Original Message----- >>>>>> From: Serge Blazhiyevskyy [mailto:[email protected]] >>>>>> Sent: Thursday, October 11, 2012 5:35 PM >>>>>> To: [email protected]; murthy nvvs >>>>>> Subject: Re: Issue when clicking on BrowseFileSystem >>>>>> >>>>>> Take a look at your conf files. Normally it is in hdfs-site.xml >>>>>> >>>>>> Look for name node name or address. Set it to loclahost or >>>>>> 127.0.0.1 >>>>>> >>>>>> That might help. >>>>>> >>>>>> Serge >>>>>> >>>>>> On 10/11/12 2:31 PM, "Andy Isaacson" <[email protected]> wrote: >>>>>> >>>>>>>What Hadoop version did you install? Can you provide the .address >>>>>>>settings for your NN and one of your DNs? If you visit >>>>>>>/dfshealth.jsp on your NN, how many live nodes and dead nodes does it >>>>>>>report? >>>>>>> >>>>>>>-andy >>>>>>> >>>>>>>On Wed, Oct 10, 2012 at 9:54 PM, murthy nvvs >>>>>>><[email protected]> >>>>>>>wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I had made Hadoop setup & set all the configuration files. >>>>>>>> when go to this url through browser http://localhost:50070, it >>>>>>>>opened well but when i clicked on BrowseTheFileSystem , its >>>>>>>>redirecting to >>>>>>>>0.0.0.0:50070/browseDirectory.jsp?namenodeinfoport=500070&dir=/ >>>>>>>> its showing some 404 error in this page. >>>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Murthy >>>>>> >>>>>> NOTICE: This e-mail message and any attachments are confidential, >>>>>> subject to copyright and may be privileged. Any unauthorized use, >>>>>> copying or disclosure is prohibited. If you are not the intended >>>>>> recipient, please delete and contact the sender immediately. >>>>>> Please consider the environment before printing this e-mail. AVIS >>>>>> : le présent courriel et toute pièce jointe qui l'accompagne sont >>>>>> confidentiels, protégés par le droit d'auteur et peuvent être >>>>>> couverts par le secret professionnel. Toute utilisation, copie ou >>>>>> divulgation non autorisée est interdite. Si vous n'êtes pas le >>>>>> destinataire prévu de ce courriel, supprimez-le et contactez >>>>>> immédiatement l'expéditeur. >>>>>> Veuillez penser à l'environnement avant d'imprimer le présent >>>>>> courriel >>>>> >>>>> >>>>> >>>>> -- >>>>> Harsh J >>>>> NOTICE: This e-mail message and any attachments are confidential, >>>>> subject to copyright and may be privileged. Any unauthorized use, >>>>> copying or disclosure is prohibited. If you are not the intended >>>>> recipient, please delete and contact the sender immediately. Please >>>>> consider the environment before printing this e-mail. AVIS : le >>>>> présent courriel et toute pièce jointe qui l'accompagne sont >>>>> confidentiels, protégés par le droit d'auteur et peuvent être >>>>> couverts par le secret professionnel. Toute utilisation, copie ou >>>>> divulgation non autorisée est interdite. Si vous n'êtes pas le >>>>> destinataire prévu de ce courriel, supprimez-le et contactez >>>>> immédiatement l'expéditeur. >>>>> Veuillez penser à l'environnement avant d'imprimer le présent >>>>> courriel >>>> NOTICE: This e-mail message and any attachments are confidential, >>>> subject to copyright and may be privileged. Any unauthorized use, >>>> copying or disclosure is prohibited. If you are not the intended >>>> recipient, please delete and contact the sender immediately. Please >>>> consider the environment before printing this e-mail. AVIS : le >>>> présent courriel et toute pièce jointe qui l'accompagne sont >>>> confidentiels, protégés par le droit d'auteur et peuvent être >>>> couverts par le secret professionnel. Toute utilisation, copie ou >>>> divulgation non autorisée est interdite. Si vous n'êtes pas le >>>> destinataire prévu de ce courriel, supprimez-le et contactez immédiatement >>>> l'expéditeur. >>>> Veuillez penser à l'environnement avant d'imprimer le présent >>>> courriel >>> NOTICE: This e-mail message and any attachments are confidential, >>> subject to copyright and may be privileged. Any unauthorized use, >>> copying or disclosure is prohibited. If you are not the intended >>> recipient, please delete and contact the sender immediately. Please >>> consider the environment before printing this e-mail. AVIS : le >>> présent courriel et toute pièce jointe qui l'accompagne sont >>> confidentiels, protégés par le droit d'auteur et peuvent être >>> couverts par le secret professionnel. Toute utilisation, copie ou >>> divulgation non autorisée est interdite. Si vous n'êtes pas le >>> destinataire prévu de ce courriel, supprimez-le et contactez immédiatement >>> l'expéditeur. >>> Veuillez penser à l'environnement avant d'imprimer le présent >>> courriel >> NOTICE: This e-mail message and any attachments are confidential, >> subject to copyright and may be privileged. Any unauthorized use, >> copying or disclosure is prohibited. If you are not the intended >> recipient, please delete and contact the sender immediately. Please >> consider the environment before printing this e-mail. AVIS : le >> présent courriel et toute pièce jointe qui l'accompagne sont >> confidentiels, protégés par le droit d'auteur et peuvent être couverts >> par le secret professionnel. Toute utilisation, copie ou divulgation >> non autorisée est interdite. Si vous n'êtes pas le destinataire prévu >> de ce courriel, supprimez-le et contactez immédiatement l'expéditeur. >> Veuillez penser à l'environnement avant d'imprimer le présent courriel > NOTICE: This e-mail message and any attachments are confidential, subject to > copyright and may be privileged. Any unauthorized use, copying or disclosure > is prohibited. If you are not the intended recipient, please delete and > contact the sender immediately. Please consider the environment before > printing this e-mail. AVIS : le présent courriel et toute pièce jointe qui > l'accompagne sont confidentiels, protégés par le droit d'auteur et peuvent > être couverts par le secret professionnel. Toute utilisation, copie ou > divulgation non autorisée est interdite. Si vous n'êtes pas le destinataire > prévu de ce courriel, supprimez-le et contactez immédiatement l'expéditeur. > Veuillez penser à l'environnement avant d'imprimer le présent courriel
