Unfortunate error message when missing ACLs about waterdrop HOT 8 CLOSED

Sync

from waterdrop.

Async or sync publishing?

from waterdrop.

@paneq p e.cause - this should contain the raw details on why wasn't delivered. Does it work?

from waterdrop.

@mensfeld

Unfortunately, it does not. e.cause is nil.

from waterdrop.

Replication procedure:

• clone https://github.com/paneq/kafka_docker_sasl_plain
• run docker-compose -f test.yml up
• execute:

WaterDrop.setup do |config|
  config.deliver = true
  config.client_id = "my-app-waterdrop"
  config.kafka.seed_brokers = ["kafka://127.0.0.1:9092"]

  config.kafka.ssl_ca_certs_from_system = false
  config.kafka.sasl_over_ssl = false
  config.kafka.sasl_plain_username = "edward"
  config.kafka.sasl_plain_password = "edward"
end


WaterDrop::SyncProducer.call('message', topic: 'unexisting')
# => Failed to assign partitions to 1 messages (Kafka::DeliveryFailed)

compare that with:

kafka = Kafka.new(
	["127.0.0.1:9092"], 
	client_id: "my-application",
	sasl_plain_username: 'edward',
        sasl_plain_password: 'edward',
	sasl_over_ssl: false,
)

kafka.deliver_message("message", topic: "unexisting")
# => Kafka::TopicAuthorizationFailed

and that should suffice.

FYI: Authentication and authorization is configured here: https://github.com/paneq/kafka_docker_sasl_plain/blob/master/test.yml#L23L36

If something does not work, let me know.

from waterdrop.

I can confirm. Investigating and fixing...

from waterdrop.

This is a mismatch in between how delivery boy works and how ruby-kafka client works. It won't be fixed due to #106

For rdkafka there's a issue reported: karafka/rdkafka-ruby#92

from waterdrop.

I will close it. This should be fixed in librdkafka and we're moving out from ruby-kafka.

from waterdrop.