There was a big transaction which contains millions of data update. And it crashed Debezium with OOM. 

When the big transaction was handling, there's no Debezium info/warn log printed. The issue was noticed until TRACE level was open.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Oracle 1.9.0.Final

What is the connector configuration?

Please check config.json

What is the captured database version and mode of depoyment?

19c

What behaviour do you expect?

Debezium should be able to skip this kind of transaction since it's not able to handle it successfully.

What behaviour do you see?

OOM

Do you see the same behaviour using the latest relesead Debezium version?

No. Hasn't tried 2.0 yet.

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

Please check attatch.log

How to reproduce the issue using our tutorial deployment?

Update enough data (millions) in one transaction. 

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

I think we need a new configuration for data limitation in same transaction. Once the threshold is reached, then mark the transaction as discarded. Discard all received data in the transaction and also all of following data of same transaction. And finally discard the transaction when it is finished. Print logs and send metrics at the same time.