Also I see thousands of this logs in the broker log. I think this isn't wanted, or? But severity is INFO Still no idea how to get the queues empty.

{"log":"2024-03-27T16:27:32,130+0000 [pulsar-io-3-1] INFO  org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.28.12.64:55450\n","stream":"stdout","time":"2024-03-27T16:27:32.130797861Z"}
{"log":"2024-03-27T16:27:32,133+0000 [pulsar-io-3-2] INFO  org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.28.27.22:34284\n","stream":"stdout","time":"2024-03-27T16:27:32.133357757Z"}
{"log":"2024-03-27T16:27:32,133+0000 [pulsar-io-3-3] INFO  org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.28.27.22:34298\n","stream":"stdout","time":"2024-03-27T16:27:32.133827432Z"}
{"log":"2024-03-27T16:27:32,148+0000 [pulsar-io-3-5] INFO  org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.28.16.46:60874\n","stream":"stdout","time":"2024-03-27T16:27:32.149161337Z"}
{"log":"2024-03-27T16:27:32,149+0000 [pulsar-io-3-6] INFO  org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.28.16.46:60878\n","stream":"stdout","time":"2024-03-27T16:27:32.149671807Z"}
{"log":"2024-03-27T16:27:32,151+0000 [pulsar-io-3-7] INFO  org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.28.20.18:42816\n","stream":"stdout","time":"2024-03-27T16:27:32.151386137Z"}
{"log":"2024-03-27T16:27:32,151+0000 [pulsar-io-3-8] INFO  org.apache.pulsar.broker.service.ServerCnx - Closed connection from /10.28.20.18:42824\n","stream":"stdout","time":"2024-03-27T16:27:32.151785968Z"}

These messages are “normal” and not indicative of an error. If you find these annoying, you can always change the logging level to WARN in the log4j configuration.

Thanks! Was just wondering during my search for my problem