Adding Tables to xCluster Replication Fails : Could not find tableId – Yugabyte

Issue:
When adding new tables to an existing non-transactional xCluster replication configuration in YugabyteDB, the operation may fail with an error referencing a missing tableId.

This typically occurs if an index related to a replicated base table was created after replication was set up and was not added to the xCluster configuration.

Symptoms

Adding tables to an xCluster replication fails with below error. The reported tableId usually corresponds to an index object in this case. Base table is already in replication, but the newly created index is not.

Edit tables request failed: HTTP Server Error.
Unexpected exception[CompletionException: java.lang.RuntimeException:
Could not find tableId (<tableId>) in the xCluster config with uuid (<configId>)]

Cause

In non-transactional xCluster replication, all base tables and their associated index tables must be included in the replication configuration.

When replication is first created, indexes on the base tables are included. If a new index is created after replication setup, it is not automatically added. Refer to the related document - xCluster DDL Order of Operations

Resolution

Identify the tableId reported in the error and check whether it corresponds to an index using Master UI(Source Master UI -> tables and search of tabletID ) OR using yb-admin on source.

yb-admin --master_addresses <source_master_addresses> list_tables include_table_id | grep <tableId>
Verify if the index belongs to a base table that is already in replication
Add the missing index table(s) to the replication configuration.
Retry the table addition.

Related articles