Errors might appear when you try to replicate HBase data from existing tables and
future tables in a database using the “Replicate Database” option during the HBase
replication policy creation process. These errors appear when there are compatibility
issues.
The following list shows a few errors that might appear and how to mitigate
these issues:
-
The error Destination cluster doesn't support replication of all
HBase tables. Please change the destination cluster or specify the
tables that should be replicated. appears during HBase
replication policy creation process. How to mitigate this issue?
This error appears if you choose the option during the HBase replication policy creation
process for unsupported cluster versions.
To mitigate this issue,
ensure that the target Cloudera Manager version is 7.11.0 or higher
and the source cluster version is CDH 6.x or higher before you
choose the option during the HBase replication policy creation
process.
-
The error Exception in thread "main"
java.lang.IllegalArgumentException: Cannot add a peer
with
id=_repl__f1907207cdbc4a528777bb4a316_ba23f09f7328494bbcbf81f40b
because that id already exists appears after
creating subsequent HBase replication policies.
This error appears if you created an HBase peer manually using the
hbase shell to replicate all column families on a
source cluster using CDH 5.x.
You can replicate the HBase
data (existing tables and future tables) in a database only if the
target Cloudera Manager version is 7.11.0 or higher and the source
cluster version is CDH 6.x or higher. Therefore, even if you create
a peer using hbase shell in the source cluster version
CDH 5.16.2 or any other unsupported version, errors might
appear.
