Created 07-18-2018 01:29 AM
I am testing BDR functionality and have not managed to create a working Hive replication job yet. Currently when running it I am getting
Message: The remote command failed with error message: Another Hive replication command is already running for Database: MY_TABLE_NAME Table: . on service HIVE-2.
I previously had Hive replication failing immediately because I had not specified the port (443) for the CM peering.
What is causing this to fail immediately? I cannot see any logs apart from the above error message.
I happen to be copying betwee two clusters within the same Cloudera Manager - but wont always be.
Any ideas?
thanks
Created 08-01-2018 02:11 AM
Created 08-27-2018 10:49 PM
A peer is normally only created if replicating from a cluster that has another Cloudera Manager.
If you have two clusters using the same Cloudera Manager, your replication schedule should let you choose which Hive server and cluster will be the source and target.
If that isn't working out, please show a screen shot of what selections are availavble in your replication schedule.
Created 08-28-2018 02:00 PM
I talked with the Cloudera engineering team and indeed, you are not supposed to create a peer from/to the same CM instance. In fact, our UI blocks that unless you trick it by using a different hostname or ip address.
We will work on improving our documentaiton to explain how to replicate between clusters managed by the same Cloudera Manager.
If you have any follow-up questions, we're happy to help.
Ben
Created 08-29-2018 02:40 AM