Replies: 2 comments 1 reply
-
This doesn't sound related to this repository I would recommend raising an issue on the CDC connector repository And attach logs of the connector and scylla |
Beta Was this translation helpful? Give feedback.
0 replies
-
@amitesh88 - isn't this a duplicate of scylladb/scylla-cdc-source-connector#47 ? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have our multi dc setup with 3 node in dc1 and 3 in dc2 . Although both the DCs are in the same region n same subnet, This is done as we require separate clusters for reading n writing data.
Our setup creates a new table everyday at 12 midnight with cdc enabled in DC1
At the same time we also create a kafka debezium source connector to consume cdc logs from DC2 everyday
Issue:
At around 12
When creating a new source con , we observe scylladb servers on dc2 consumes 100% cpu.
We increased cpu from 16cores to 32 but still same behavior
Once the kafka connector creates its topic and start reading data from cdc log ,scylladb cpu cools down
Logs:
The logs in syslog shows reader_concurrency_semaphores for that time period.
Any expert thoughts is appreciated
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions