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

JMX metric TotalTableCount appears broken after 1.1.0.CR1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • 1.1.0.Final, 1.1.1.Final, 1.2.0.Alpha1
    • postgresql-connector
    • None
    • Hide

      1. I set-up debezium postgres connector with config:

          "connector.class": "io.debezium.connector.postgresql.PostgresConnector",
          "database.hostname": "$TIMESCALEDB_HOST",
          "tasks.max": ${DEBEZIUM_NUM_TASKS:-1},
          "database.port": "5432",
          "database.user": "$TIMESCALEDB_USERNAME",
          "database.password": "$TIMESCALEDB_PASSWORD",
          "database.dbname": "verifi_itm",
          "database.server.name": "cdc",
          "schema.whitelist": "myschema",
          "table.whitelist": "table1,table2,table3,table4",
          "key.converter": "org.apache.kafka.connect.json.JsonConverter",
          "value.converter": "org.apache.kafka.connect.json.JsonConverter",
          "key.converter.schemas.enable":"false",
          "value.converter.schemas.enable": "false",
          "heartbeat.interval.ms": 5000,
          "heartbeat.topics.prefix": "heartbeat",
          "snapshot.mode": "exported",
          "plugin.name": "wal2json_streaming"
      

      2. Run the connector and use our cdc tests to check whether the connector is publishing changes from tracked table.

      3. Observe the MBean attribute TotalTableCount. I use prometheus java agent to export JMX MBeans and look at the debezium_postgres_connector_metrics_totaltablecount attribute.

      4. The expected value is 4 because 4 tables are being tracked, but it now remains 0.

      Show
      1. I set-up debezium postgres connector with config: "connector.class": "io.debezium.connector.postgresql.PostgresConnector", "database.hostname": "$TIMESCALEDB_HOST", "tasks.max": ${DEBEZIUM_NUM_TASKS:-1}, "database.port": "5432", "database.user": "$TIMESCALEDB_USERNAME", "database.password": "$TIMESCALEDB_PASSWORD", "database.dbname": "verifi_itm", "database.server.name": "cdc", "schema.whitelist": "myschema", "table.whitelist": "table1,table2,table3,table4", "key.converter": "org.apache.kafka.connect.json.JsonConverter", "value.converter": "org.apache.kafka.connect.json.JsonConverter", "key.converter.schemas.enable":"false", "value.converter.schemas.enable": "false", "heartbeat.interval.ms": 5000, "heartbeat.topics.prefix": "heartbeat", "snapshot.mode": "exported", "plugin.name": "wal2json_streaming" 2. Run the connector and use our cdc tests to check whether the connector is publishing changes from tracked table. 3. Observe the MBean attribute TotalTableCount. I use prometheus java agent to export JMX MBeans and look at the debezium_postgres_connector_metrics_totaltablecount attribute. 4. The expected value is 4 because 4 tables are being tracked, but it now remains 0.

    Description

      We recently upgraded from 1.1.0.Beta2 to 1.1.0.Final and saw that this metric now only reports a 0. Downgrading it to 1.1.0.CR1 or 1.1.0Beta2 fixes it. I have not verified whether other metrics are affected too.

      Attachments

        Activity

          People

            jpechane Jiri Pechanec
            ayushsagar Ayush Sagar (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: