Re: An issue with Hive on hadoop cluster -- Resolved

Finally Got It ! Here's the full story I started with running hive on a single node hadoop cluster. And our metastore was on a mysql instance. At that time, namenode uri was localhost:54310 Then it was decided to add more nodes to the cluster. And modified all the *-site.xml files where ever rele

Re: An issue with Hive on hadoop cluster

Thanks for the suggestions. I had tried out by specifying only the ips instead of hostnames, but now I modified the /etc/hosts file as suggested below, appropriately. Still no success. If I use IPs instead of hostnames I get the below error in the hive cli. *2011-05-24 14:42:53,485 ERROR ql.Drive

Re: An issue with Hive on hadoop cluster

Hi, I had similar problems when I was setting up my hadoop cluster. The Datanodes where trying to access localhost instead of my namenode. To fix this issue I modified my /etc/hosts file on all my nodes (namenode + datanodes) in such a way that the first line corresponds to the binding hostname>.

Re: An issue with Hive on hadoop cluster

I have the configuration consistent across both the client and server sides. I have checked the hadoop logs on both the nodes. On both the nodes, in the tasktracker logs, every task attempt is directed towards hdfs://localhost:54310/user/hive/warehouse and not towards hdfs://:54310/user/hive/wareh

Re: An issue with Hive on hadoop cluster

AFAIK, the fs.default.name should be set by both the client and server side .xml files, and they should be consistent (the URI scheme, the hostname and port number). The server side config (also called fs.default.name) should be read by the namenod

Re: An issue with Hive on hadoop cluster

I have already tried your suggestion. I have mentioned the same in my mail. I have also given the required permissions for the directory (hive.metastore.warehouse.dir). If you look closely at the stack trace , the port number that I have specified in the config files for the namenode and jobtracke

Re: An issue with Hive on hadoop cluster

Set the follow property in hive.site.xml. fs.default.name = hdfs: mapred.job.tracker = hive.metastore.warehouse.dir = Make sure you have the authority to write into this directory (hive.metastore.warehouse.dir). Try it. 2011/5/23 MIS > I'm getting into an issue when trying to run hive over t

An issue with Hive on hadoop cluster

I'm getting into an issue when trying to run hive over the hadoop cluster. The hadoop cluster is working fine, in a stand alone manner. I'm using hadoop 0.20.2 and hive 0.7.0 versions. The problem is that the hive is not considering the fs.default.name property that I am setting in the core-site.