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

SignalsIT times out after 6h on CI

    XMLWordPrintable

Details

    Description

      See https://github.com/debezium/debezium/runs/4347516302?check_suite_focus=true

      There's this in the logs:

      2021-11-27T00:53:18.4900524Z org.postgresql.util.PSQLException: ERROR: unrecognized pgoutput option: messages
      2021-11-27T00:53:18.4903009Z   Where: slot "debezium", output plugin "pgoutput", in the startup callback
      2021-11-27T00:53:18.4904731Z 	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565)
      2021-11-27T00:53:18.4907470Z 	at org.postgresql.core.v3.QueryExecutorImpl.processCopyResults(QueryExecutorImpl.java:1224)
      2021-11-27T00:53:18.4909959Z 	at org.postgresql.core.v3.QueryExecutorImpl.readFromCopy(QueryExecutorImpl.java:1124)
      2021-11-27T00:53:18.4911914Z 	at org.postgresql.core.v3.CopyDualImpl.readFromCopy(CopyDualImpl.java:44)
      2021-11-27T00:53:18.4914889Z 	at org.postgresql.core.v3.replication.V3PGReplicationStream.receiveNextData(V3PGReplicationStream.java:160)
      2021-11-27T00:53:18.4918577Z 	at org.postgresql.core.v3.replication.V3PGReplicationStream.readInternal(V3PGReplicationStream.java:125)
      2021-11-27T00:53:18.4921519Z 	at org.postgresql.core.v3.replication.V3PGReplicationStream.readPending(V3PGReplicationStream.java:82)
      2021-11-27T00:53:18.4924857Z 	at io.debezium.connector.postgresql.connection.PostgresReplicationConnection$1.readPending(PostgresReplicationConnection.java:479)
      2021-11-27T00:53:18.4930070Z 	at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.searchWalPosition(PostgresStreamingChangeEventSource.java:316)
      2021-11-27T00:53:18.4935098Z 	at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:153)
      2021-11-27T00:53:18.4939438Z 	at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:41)
      2021-11-27T00:53:18.4952532Z 	at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:172)
      2021-11-27T00:53:18.4956160Z 	at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:139)
      2021-11-27T00:53:18.4959515Z 	at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:108)
      2021-11-27T00:53:18.4961532Z 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
      2021-11-27T00:53:18.4962895Z 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
      2021-11-27T00:53:18.4964534Z 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
      2021-11-27T00:53:18.4966371Z 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
      2021-11-27T00:53:18.4967598Z 	at java.base/java.lang.Thread.run(Thread.java:833)
      

      Setting the "messages" parameter was introduced via DBZ-2363; we may only set it if the DB is version 14 or newer (it was only added in 14), as passing an unknown option will fail (in fact, this change as-is breaks support with pgoutput on versions 10 - 13).

      What's not clear is why the test does not stop and fail when not receing events after some time?

      Attachments

        Activity

          People

            Unassigned Unassigned
            gmorling@redhat.com Gunnar Morling
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: