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

ExtractNewRecordState SMT spamming logs for heartbeat messages

XMLWordPrintable

    • Hide

      1. Connect Debezium, with a root logging level of at least WARNING to a postgres DB with some kind of table whitelist that does not encompass all the tables.
      2. Wait for the snapshot to complete.
      3. Insert a row into one of the tables the whitelist doesn't cover.

      You should see the Expected Envelope for transformation, passing it unchanged message in the logs.

      Show
      1. Connect Debezium, with a root logging level of at least WARNING to a postgres DB with some kind of table whitelist that does not encompass all the tables. 2. Wait for the snapshot to complete. 3. Insert a row into one of the tables the whitelist doesn't cover. You should see the Expected Envelope for transformation, passing it unchanged message in the logs.

      If you specify a whitelist of topics for the connector in a configuration where you are using ExtractNewRecordState, you can expect to see a steady stream of messages of Expected Envelope for transformation, passing it unchanged at the WARNING log level, which, it turns out, corresponds to a heartbeat message for tables that are NOT specified in the whitelist, but have had some kind of change done to them. The heartbeat message should probably be dropped before it hits the transformation chain. This is mainly an annoyance to clean logs more than anything else, but it would be nice to not have to boost the SmtManager module's logging level to ERROR in order to mask this.

      (I've observed this on 1.0.3.Final, but from the code, it looks like it should happen in later versions as well)

              ccranfor@redhat.com Chris Cranford
              asaf-1 Asaf Flescher (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: