-
Bug
-
Resolution: Unresolved
-
Major
-
3.2.2.Final
-
None
-
False
-
-
False
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
<2.5.2>
What is the connector configuration?
<
snapshot.mode=initial
max.queue.size=81290
max.batch.size=20480
snapshot.max.threads=2
snapshot.transaction.isolation=read_committed
snapshot.locking.mode=none
incremental.snapshot.chunk.size=2000
snapshot.fetch.size=1000
snapshot.transaction.isolation=read_committed
>
What is the captured database version and mode of deployment?
(E.g. on-premises, with a specific cloud provider, etc.)
<io.debezium.connector.oracle.OracleConnector>
What behavior do you expect?
<No OOM should happen. Is this a already reported problem?>
What behavior do you see?
<
- Using a CDCCapture node with a huge Oracle DataBase is causing the JVM in the Integration Server to crash even with a very large JVMMaxHeapSize. I tried tuning the JVM Stack Size for the customer to see if it would reduce the overall heap size, but it did not help. Customer currently has the JVMMaxHeapSize set to 12 GB, and it is crashing with a JVM Out of Memory after about 12 hours.
OOM happening after 12 hours>
Do you see the same behaviour using the latest released Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
<Not tested yet>
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
<NO>
How to reproduce the issue using our tutorial deployment?
<N/A>
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<OOM should not happen>
Implementation ideas (optional)
<Your answer>