11-12-2015 10:23 AM - last edited on 11-08-2016 08:42 AM by cjervis
I'm having issues with running Hive replication jobs (these worked previously in the past), but due to some unknown system/configuration changes these jobs are now aborting almost immediately in the "Export Remote Hive Metastore" phase. I've been hunting around on both the source and target clusters and I'm unable to find any trace of log files for this job. Does anyone know where I should be looking for this information?
So far I've looked in:
/var/log/hive on local filesystems where Hive Metastore and Hive Server are running
/user/hdfs/.cm/hive on target cluster
/var/run/cloudera-scm-agent/process/* on all nodes in both clusters
11-20-2015 05:56 AM
I found out what I was doing wrong - I had a node on the source cluster with the Hive gateway role installed, but it wasn't configured 100% correctly. For some reason when the BDR jobs were launched, they kept running on this node and immediately failing so I wasn't getting any errors. The export metastore step of the Hive Replication job will run on a source cluster node that has either the HiveServer or Hive Gateway role installed
11-20-2015 06:28 AM
Congratulations on solving your issue TylerHale. Hopefully your solution will be able to help others who run into the same problem. Thanks for sharing! :)
07-11-2019 03:58 PM
Hi @Daggers ,
For which logs are you looking?
Hive Metadata Export generally happens on the *source* cluster, so you should be able to find the command and associated logs by logging into the source cluster's Cloudera Manager, navigating to the Hive service and clicking the "Commands" subtab. You can then look at the results of the command for more information. If the command contains stderr/stdout logs, the top few lines should include the host on which the command ran, too.