Event sourcing with kafka for REST API

[1indiangirl]

trying to configure event sourcing with kafka to get msgs when there any CRUD for inmemory apicurio registry with REST API.
Taking reference from : https://www.apicur.io/registry/docs/apicurio-registry/2.2.x/getting-started/assembly-configuring-the-registry.html#registry-cloud-events_registry

not able to see any msgs sent to confugred kafka topic Also there are only warning msgs related kafka in cmd logs.

please help with the same on how to correct configuration with example.

[EricWittmann]

Are you seeing any error messages in the server logs or is it simply silent and not working?

[1indiangirl]

2022-10-03 10:49:39 WARN <> [org.apache.kafka.clients.NetworkClient] (kafka-producer-network-thread | producer-1) [Producer clientId=producer-1] Connection to node -1 (localhost/127.0.0.1:29092) could not be established. Broker may not be available.
2022-10-03 10:49:39 WARN <> [org.apache.kafka.clients.NetworkClient$DefaultMetadataUpdater] (kafka-producer-network-thread | producer-1) [Producer clientId=producer-1] Bootstrap broker localhost:29092 (id: -1 rack: null) disconnected
2022-10-03 10:49:40 WARN <> [null] (vertx-blocked-thread-checker) Thread Thread[vert.x-eventloop-thread-0,5,main] has been blocked for 44044 ms, time limit is 2000 ms: io.vertx.core.VertxException: Thread blocked
        at [email protected]/java.lang.Object.wait(Native Method)
        at app//org.apache.kafka.common.utils.SystemTime.waitObject(SystemTime.java:55)
        at app//org.apache.kafka.clients.producer.internals.ProducerMetadata.awaitUpdate(ProducerMetadata.java:119)
        at app//org.apache.kafka.clients.producer.KafkaProducer.waitOnMetadata(KafkaProducer.java:1047)
        at app//org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProducer.java:906)
        at app//org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:885)
        at app//io.apicurio.registry.utils.kafka.AsyncProducer.apply(AsyncProducer.java:63)
        at app//io.apicurio.registry.utils.kafka.AsyncProducer.apply(AsyncProducer.java:41)
        at app//io.apicurio.registry.events.kafka.KafkaEventSink.handle(KafkaEventSink.java:107)
        at app//io.apicurio.registry.events.kafka.KafkaEventSink_ClientProxy.handle(Unknown Source)
        at app//io.apicurio.registry.events.EventsServiceImpl$$Lambda$424/0x0000000840485840.handle(Unknown Source)
        at app//io.vertx.core.impl.EventLoopContext.emit(EventLoopContext.java:50)
        at app//io.vertx.core.impl.DuplicatedContext.emit(DuplicatedContext.java:168)
        at app//io.vertx.core.eventbus.impl.MessageConsumerImpl.dispatch(MessageConsumerImpl.java:177)
        at app//io.vertx.core.eventbus.impl.HandlerRegistration$InboundDeliveryContext.next(HandlerRegistration.java:169)
        at app//io.vertx.core.eventbus.impl.HandlerRegistration$InboundDeliveryContext.dispatch(HandlerRegistration.java:134)
        at app//io.vertx.core.eventbus.impl.HandlerRegistration$$Lambda$525/0x00000008405b7c40.run(Unknown Source)
        at app//io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:111)
        at app//io.vertx.core.eventbus.impl.HandlerRegistration.dispatch(HandlerRegistration.java:105)
        at app//io.vertx.core.eventbus.impl.MessageConsumerImpl.deliver(MessageConsumerImpl.java:183)
        at app//io.vertx.core.eventbus.impl.MessageConsumerImpl.doReceive(MessageConsumerImpl.java:168)
        at app//io.vertx.core.eventbus.impl.HandlerRegistration.lambda$receive$0(HandlerRegistration.java:56)
        at app//io.vertx.core.eventbus.impl.HandlerRegistration$$Lambda$524/0x00000008405b7840.run(Unknown Source)
        at app//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
        at app//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
        at app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:503)
        at app//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
        at app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at [email protected]/java.lang.Thread.run(Thread.java:829)

these are the logs that i see whenever new activity is done on in mem-registry
in configuration able to see topic name but after activity nothing is sent to topic

[EricWittmann]

It seems to me that the key information in the logs is this:

Connection to node -1 (localhost/127.0.0.1:29092) could not be established.

If you are running the registry as a container image, perhaps you need to update your configuration to use proper container routing? If you're not using containers, can you confirm that Kafka is available on 127.0.0.0 on port 29092?