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

How to protect memory via using LogMiner

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 1.4.0.Alpha2
    • oracle-connector
    • False
    • False
    • Undefined

      The configuration way is logminer.

      I found that the redo log data is stored in memory by callback, and not invoke dispatchDataChangeEvent, until operationCode is commit. 

      If the large data is updated from the same transcation, the memory is overused.

      How can I avoid a large memory footprint.

       

              ccranfor@redhat.com Chris Cranford
              benbenguo Dean Kwok (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: