[CDCSDK] Data loss seen in CDC with single shard transactions #19294
Labels
2.20.6_blocker
area/cdcsdk
CDC SDK
area/ycql
Yugabyte CQL (YCQL)
kind/bug
This issue is a bug
priority/highest
Highest priority issue
qa_automation
Bugs identified via itest-system, LST, Stress automation or causing automation failures
qa_stress
Bugs identified via Stress automation
Jira Link: DB-8105
Description
Please find run report in JIRA
This is without tablet splitting as well
AssertionError: Change is the same for 30 minutes test_cdc_bc296a yb=88200 sink=88118. Replication stopped at 2023-09-25T15:52:37.491598
Source connector version
Custom connector: quay.io/vaibhav_yb/test_repo:1.9.5.y.34.ycql-2
1.9.5.y.34-SNAPSHOT
Connector configuration
add connector connector_name='ybconnector_cdc_66697c_test_cdc_29f1e0_test_cdc_bc296a' stream_id='781623c7cd2f4faf9928b986b08c8994' db_name='cdc_66697c' connector_host='172.151.26.81' table_list=['test_cdc_29f1e0', 'test_cdc_bc296a'] {'name': 'ybconnector_cdc_66697c_test_cdc_29f1e0_test_cdc_bc296a', 'config': {'connector.class': 'io.debezium.connector.yugabytedb.YugabyteDBConnector', 'database.hostname': '172.151.22.115', 'database.master.addresses': '172.151.22.115:7100,172.151.19.235:7100,172.151.16.252:7100', 'database.port': 9042, 'database.masterhost': '172.151.22.115', 'database.masterport': '7100', 'database.user': 'cassandra', 'database.password': 'cassandra', 'database.dbname': 'cdc_66697c', 'database.server.name': 'db_cdc', 'database.streamid': '781623c7cd2f4faf9928b986b08c8994', 'snapshot.mode': 'never', 'admin.operation.timeout.ms': 600000, 'socket.read.timeout.ms': 600000, 'max.connector.retries': '10', 'operation.timeout.ms': 600000, 'topic.creation.default.compression.type': 'lz4', 'topic.creation.default.cleanup.policy': 'delete', 'topic.creation.default.partitions': 2, 'topic.creation.default.replication.factor': '1', 'tasks.max': '5', 'table.include.list': 'cdc_66697c.test_cdc_29f1e0,cdc_66697c.test_cdc_bc296a', 'database.qltype': 'ycql'}}
YugabyteDB version
2.19.3.0-b136
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: