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

Fix persistence of consistent snapshot related details of cdcsdk stream metadata in sys_catalog #20202

Closed
yugabyte-ci opened this issue Dec 6, 2023 · 1 comment
Assignees
Labels
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 Dec 6, 2023

Jira Link: DB-9156

@yugabyte-ci yugabyte-ci added area/cdcsdk CDC SDK jira-originated kind/bug This issue is a bug priority/high High Priority status/awaiting-triage Issue awaiting triage and removed status/awaiting-triage Issue awaiting triage labels Dec 6, 2023
@asrinivasanyb
Copy link
Contributor

The cdcsdk stream metadata is updated with the consistent snapshot related details (consistent snapshot time and consistent snapshot option). However, this update is not getting persisted in sys_catalog.

asrinivasanyb added a commit that referenced this issue Dec 7, 2023
…ls of cdcsdk stream metadata in sys_catalog

Summary:
This is related to the CDC Consistent Snapshot feature (GH #18508).

The cdcsdk stream metadata is updated with the consistent snapshot related details
(consistent snapshot time and consistent snapshot option).
However, this update was not getting persisted in the sys_catalog.

This diff fixes	this bug by calling "sys_catalog_->Upsert" for the stream in question.

UPGRADE/ROLLBACK SAFETY:
Upgrade safe
Rollback safe

The CDC Consistent Snapshot feature is currently disabled.
Changes are guarded by the TEST flag yb_enable_cdc_consistent_snapshot_streams which is set to false by default.
This same flag will be redefined as an autoflag (LocalPersisted) once all
the support for this feature is in place.
Jira: DB-9156

Test Plan:
Jenkins: test regex: .*CDCSDKConsistentSnapshotTest.*

New Unit Test -
.yb_build.sh --cxx-test integration-tests_cdcsdk_consistent_snapshot-test --gtest_filter CDCSDKConsistentSnapshotTest.TestConsistentSnapshotMetadataPersistence

Reviewers: skumar, stiwary, xCluster, hsunder

Reviewed By: skumar

Subscribers: ycdcxcluster, ybase, bogdan

Differential Revision: https://phorge.dev.yugabyte.com/D30787
@yugabyte-ci yugabyte-ci reopened this Dec 14, 2023
asrinivasanyb added a commit that referenced this issue Dec 15, 2023
…t related details of cdcsdk stream metadata in sys_catalog

Summary:
**Backport Description**
The merge was clean

**Original Description**
Original commit: 0053554 / D30787
This is related to the CDC Consistent Snapshot feature (GH #18508).

The cdcsdk stream metadata is updated with the consistent snapshot related details
(consistent snapshot time and consistent snapshot option).
However, this update was not getting persisted in the sys_catalog.

This diff fixes	this bug by calling "sys_catalog_->Upsert" for the stream in question.

UPGRADE/ROLLBACK SAFETY:
Upgrade safe
Rollback safe

The CDC Consistent Snapshot feature is currently disabled.
Changes are guarded by the TEST flag yb_enable_cdc_consistent_snapshot_streams which is set to false by default.
This same flag will be redefined as an autoflag (LocalPersisted) once all
the support for this feature is in place.
Jira: DB-9156

Test Plan:
Jenkins: test regex: .*CDCSDKConsistentSnapshotTest.*

New Unit Test -
./yb_build.sh --cxx-test integration-tests_cdcsdk_consistent_snapshot-test --gtest_filter CDCSDKConsistentSnapshotTest.TestConsistentSnapshotMetadataPersistence

Reviewers: skumar, stiwary, xCluster, hsunder

Reviewed By: skumar

Subscribers: bogdan, ybase, ycdcxcluster

Tags: #jenkins-ready

Differential Revision: https://phorge.dev.yugabyte.com/D31114
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cdcsdk CDC SDK jira-originated kind/bug This issue is a bug priority/high High Priority
Projects
None yet
Development

No branches or pull requests

2 participants