Hi, The problem I think I have is that on every TT node there is a hive-site/hive-default files, that are probably picked up and used instead of the setting I want. As those files point to a local derby my hive actions fail..
Any suggestions how can I change this behavior? Boris. On Tue, Jul 10, 2012 at 8:47 PM, Boris Shulman <[email protected]> wrote: > Hey Harsh, > > Is it possible that local hive-default.xml file is picked up from the TT > machine? If yes how can I fix this behavior as it is not possible for me to > change all the hive-default.xml files on all the nodes. The hive > configuration options show the correct values and not the localhost ones. > > Thanks, > > Boris. > > On Tue, Jul 10, 2012 at 8:07 PM, Harsh J <[email protected]> wrote: > >> Hey Boris, >> >> What do you specify as the hostname for your DB in the Hive >> configuration? Do you specify 'localhost'? If so, it will not work in >> a distributed cluster, as Oozie's actions are run as Jobs with tasks >> executing on TT machines (remotely), and they can't all have >> connections to localhost for a DB being valid logically. >> >> On Wed, Jul 11, 2012 at 8:22 AM, Boris Shulman <[email protected]> >> wrote: >> > Hi my hive action fails with: >> > >> > Failing Oozie Launcher, Main class >> > [org.apache.oozie.action.hadoop.HiveMain], exit code [10] >> > >> > >> > javax.jdo.JDOFatalDataStoreException: java.net.ConnectException : >> > Error connecting to server localhost on port 1527 with message >> > Connection refused >> > >> > >> > it looks like it can't pick-up the right hive-defaults.xml file. I have >> > changed the hive metastore to a SQL db in every possible place >> (hive-site, >> > hive-defaults), I also provided hive-default via job-config element, >> but it >> > still using the default value that I can't find where it is coming from. >> > >> > Any suggestions where it can pick the value from (I am using oozie 3.2.0 >> > and hive 0.7.1)? >> >> >> >> -- >> Harsh J >> > >
