Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CDC] Use yb_disable_catalog_version_check with logical replication connector #25716

Closed
yugabyte-ci opened this issue Jan 22, 2025 · 0 comments · Fixed by yugabyte/debezium#169
Assignees
Labels
2024.2.2_blocker area/cdc Change Data Capture area/cdcsdk CDC SDK jira-originated kind/bug This issue is a bug priority/high High Priority

Comments

@yugabyte-ci
Copy link
Contributor

yugabyte-ci commented Jan 22, 2025

Jira Link: DB-14986

@yugabyte-ci yugabyte-ci added area/cdc Change Data Capture area/cdcsdk CDC SDK jira-originated kind/bug This issue is a bug priority/high High Priority status/awaiting-triage Issue awaiting triage labels Jan 22, 2025
@yugabyte-ci yugabyte-ci added 2024.2.2_blocker and removed status/awaiting-triage Issue awaiting triage labels Jan 28, 2025
vaibhav-yb added a commit to yugabyte/debezium that referenced this issue Jan 28, 2025
…sion check for connections (#169)

## Problem

Recent changes in YugabyteDB introduced some changes where the
`relcache/catcache` is reloaded as soon as `yb_read_time` is set. Now
that caused an issue with the snapshots in the connector i.e. whenever
the connector sets the `yb_read_time` and goes on to take the snapshot
by running a `SELECT *` query, it gets the following error:

```
Caused by: io.debezium.DebeziumException: com.yugabyte.util.PSQLException: ERROR: The catalog snapshot used for this transaction has been invalidated: expected: 1, got: 0: MISMATCHED_SCHEMA
  Where: Catalog Version Mismatch: A DDL occurred while processing this query. Try again.
```

## Solution

As a workaround, we will now bypass the catalog version check by setting
a GUC `yb_disable_catalog_version_check` at the connection level so that
we do not hit the error during snapshot.

Note that we do not require this during streaming phase and since
streaming used a separate object of `ReplicationConnection` class, we
will not be modifying it.

This closes yugabyte/yugabyte-db#25716
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2024.2.2_blocker area/cdc Change Data Capture area/cdcsdk CDC SDK jira-originated kind/bug This issue is a bug priority/high High Priority
Projects
None yet
2 participants