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

Rabbitmq native stream Failed

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Alpha2
    • None
    • debezium-server
    • None
    • False
    • None
    • False

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      I use dbz to connect rabbitmq native stream, but it can not connected.

      What Debezium connector do you use and what version?

      debezium connector: postgresql

      version: 2.7

      What is the connector configuration?

      debezium.sink.type=rabbitmqstream
      debezium.sink.rabbitmqstream.connection.host=172.17.0.6
      debezium.sink.rabbitmqstream.connection.port=5552
      debezium.sink.rabbitmqstream.connection.username=root
      debezium.sink.rabbitmqstream.connection.password=root
      debezium.sink.rabbitmqstream.connection.virtual.host=test
      debezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector
      debezium.source.offset.storage.file.filename=data/offsets.dat
      debezium.source.offset.flush.interval.ms=0
      debezium.source.database.hostname=10.2.137.122
      debezium.source.database.port=5432
      debezium.source.database.user=postgres
      debezium.source.database.password=postgres
      debezium.source.database.dbname=postgres
      debezium.source.topic.prefix=local
      debezium.source.table.include.list=inventory.*
      debezium.source.plugin.name=pgoutput
      debezium.source.tombstones.on.delete=false
      debezium.source.publication.autocreate.mode=filtered
      debezium.sink.rabbitmqstream.stream=debezium_exchange
      debezium.sink.rabbitmqstream.routingKeyFromTopicName=true

      debezium.source.value.converter.schemas.enable=false

      What is the captured database version and mode of deployment?

      datbase: debezium/example-postgres:2.1

      deployment: docker

      What behavior do you expect?

      Successfully capture db

      What behavior do you see?

      error msg: "com.rabbitmq.stream.StreamException: Error while creating stream connection to fdb49ba7df14:5552. fdb49ba7df14: Name or service not known. This may be due to the usage of a load balancer that makes topology discovery fail. Use a custom AddressResolver or the --load-balancer flag if using StreamPerfTest. See https://rabbitmq.github.io/rabbitmq-stream-java-client/stable/htmlsingle/#understanding-connection-logic and https://blog.rabbitmq.com/posts/2021/07/connecting-to-streams/#with-a-load-balancer.

      Do you see the same behaviour using the latest released Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      <Your answer>

      Do you have the connector logs, ideally from start till finish?

      (You might be asked later to provide DEBUG/TRACE level log)

      <Your answer>

      How to reproduce the issue using our tutorial deployment?

      <Your answer>

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      <Your answer>

      Implementation ideas (optional)

      support  AddressResolver

      I use rabbitmq-stream-go-client is ok, the code is:

      addressResolver := stream.AddressResolver

      { Host: "10.2.3.200", Port: 15552, }

      env, err := stream.NewEnvironment(

      stream.NewEnvironmentOptions().

      SetHost(addressResolver.Host).

      SetPort(addressResolver.Port).

      SetAddressResolver(addressResolver).

      SetUser("root").SetPassword("root").SetVHost("test").

      SetMaxProducersPerClient(5))

      if err != nil

      { panic(err) }

            Unassigned Unassigned
            lucaszzy Lucas Zhang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: