Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-9636

Reduce the Oracle memory/heap cache footprint to support longer/larger transactions

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.4.0.CR1
    • None
    • oracle-connector
    • None

      What Debezium connector do you use and what version?

      3.2.4.Final

      What is the connector configuration?

      .with("snapshot.mode", "no_data")
.with("schema.history.internal.store.only.captured.tables.ddl", true)
.with("schema.history.internal.store.only.captured.databases.ddl", true)
.with("log.mining.archive.log.only.mode", false)
.with("log.mining.query.filter.mode", "in")
.with("event.processing.failure.handling.mode", "warn")
.with("errors.max.retries", 3)
.with("snapshot.max.threads", 1)
.with("log.mining.log.query.max.retries", 5)
.with("database.query.timeout.ms", 0)

      What is the captured database version and mode of deployment?

      Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production on OCI

      What behavior do you expect?

      A decrease in heap after a while

      What behavior do you see?

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

      Yes

              Unassigned Unassigned
              lucasgazire Lucas Gazire
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: