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

How to protect memory via using LogMiner

    XMLWordPrintable

Details

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

    Description

      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.

       

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users DBZ-3752 Implement a LogMiner event buffer SPI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-3123 Support long running transactions that exceed log.mining.transaction.retention.hours

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: