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

DB IO connection

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • 0.5
    • postgresql-connector
    • None

    Description

      I got to stream the changes for a few days. then suddenly it stops. If this happens, I destroy and recreate the connector and it streams again. Please see logs for reference of the error:

      [2017-04-10 08:11:47,950] WARN Closing replication stream due to db connection IO exception... (io.debezium.connector.postgresql.RecordsStreamProducer)
      [2017-04-10 08:12:44,746] INFO 10.0.0.7 - - [10/Apr/2017:08:12:44 +0000] "GET / HTTP/1.1" 200 54 0 (org.apache.kafka.connect.runtime.rest.RestServer)
      [2017-04-10 08:13:44,766] INFO 10.0.0.7 - - [10/Apr/2017:08:13:44 +0000] "GET / HTTP/1.1" 200 54 0 (org.apache.kafka.connect.runtime.rest.RestServer)
      [2017-04-10 08:14:44,786] INFO 10.0.0.7 - - [10/Apr/2017:08:14:44 +0000] "GET / HTTP/1.1" 200 54 1 (org.apache.kafka.connect.runtime.rest.RestServer)
      [2017-04-10 08:14:47,951] ERROR Exception thrown while calling task.commit() (org.apache.kafka.connect.runtime.WorkerSourceTask)
      org.apache.kafka.connect.errors.ConnectException: org.postgresql.util.PSQLException: Database connection failed when writing to copy
      at io.debezium.connector.postgresql.RecordsStreamProducer.commit(RecordsStreamProducer.java:133)
      at io.debezium.connector.postgresql.PostgresConnectorTask.commit(PostgresConnectorTask.java:154)
      at org.apache.kafka.connect.runtime.WorkerSourceTask.commitSourceTask(WorkerSourceTask.java:381)
      at org.apache.kafka.connect.runtime.WorkerSourceTask.commitOffsets(WorkerSourceTask.java:328)
      at org.apache.kafka.connect.runtime.SourceTaskOffsetCommitter.commit(SourceTaskOffsetCommitter.java:109)
      at org.apache.kafka.connect.runtime.SourceTaskOffsetCommitter.access$000(SourceTaskOffsetCommitter.java:46)
      at org.apache.kafka.connect.runtime.SourceTaskOffsetCommitter$1.run(SourceTaskOffsetCommitter.java:83)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:745)
      Caused by: org.postgresql.util.PSQLException: Database connection failed when writing to copy
      at org.postgresql.core.v3.QueryExecutorImpl.flushCopy(QueryExecutorImpl.java:942)
      at org.postgresql.core.v3.CopyDualImpl.flushCopy(CopyDualImpl.java:23)
      at org.postgresql.core.v3.replication.V3PGReplicationStream.updateStatusInternal(V3PGReplicationStream.java:176)
      at org.postgresql.core.v3.replication.V3PGReplicationStream.forceUpdateStatus(V3PGReplicationStream.java:99)
      at io.debezium.connector.postgresql.connection.PostgresReplicationConnection$1.flushLSN(PostgresReplicationConnection.java:214)
      at io.debezium.connector.postgresql.RecordsStreamProducer.commit(RecordsStreamProducer.java:128)
      ... 13 more
      Caused by: java.net.SocketException: Broken pipe
      at java.net.SocketOutputStream.socketWrite0(Native Method)
      at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
      at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
      at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
      at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
      at org.postgresql.core.PGStream.flush(PGStream.java:553)
      at org.postgresql.core.v3.QueryExecutorImpl.flushCopy(QueryExecutorImpl.java:939)
      ... 18 more

      Attachments

        Activity

          People

            jpechane Jiri Pechanec
            ssiahetiong@gmail.com Steven Siahetiong (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: