message.send.max.retries question

[ghost]

If I set message.send.max.retries=0 then if kafka is down, DeliveryReportCb is not called. Only a eventCb is called. I should suppose that message is deleted and deliveryReportCb is also called, so that the application knows which messages could not be send

[edenhill]

Huhm, I cant reproduce this with rdkafka_example_cpp:

$ echo hi | examples/rdkafka_example_cpp -P -b nonexistent.local -t fox -p 0 -X topic.message.timeout.ms=2000 -X message.send.max.retries=0
% Created producer rdkafka#producer-0
% Produced message (2 bytes)
Waiting for 1
Waiting for 1
Waiting for 1
Message delivery for (2 bytes): hi
LOG-3-GETADDR: nonexistent.local:9092/bootstrap: Failed to resolve 'nonexistent.local:9092': Name or service not known

Can you show me how to reproduce?

There was a bug that made Message.errstr() return the payload rather than the error string, but thats fixed and probably unrelated.

[ghost]

What is topic.message.timeout.ms ? can't find information in
configuration.md

On Thu, May 15, 2014 at 1:48 PM, Magnus Edenhill
notifications@github.comwrote:

Huhm, I cant reproduce this with rdkafka_example_cpp:

$ echo hi | examples/rdkafka_example_cpp -P -b nonexistent.local -t fox -p 0 -X topic.message.timeout.ms=2000 -X message.send.max.retries=0
% Created producer rdkafka#producer-0
% Produced message (2 bytes)
Waiting for 1
Waiting for 1
Waiting for 1
Message delivery for (2 bytes): hi
LOG-3-GETADDR: nonexistent.local:9092/bootstrap: Failed to resolve 'nonexistent.local:9092': Name or service not known

Can you show me how to reproduce?

There was a bug that made Message.errstr() return the payload rather than
the error string, but thats fixed and probably unrelated.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/118#issuecomment-43199971
.

[edenhill]

It is "message.timeout.ms" in the topic configuration.
The example tools allow setting topic configuration properties by prefixing with "topic." (which are stripped before being supplide to rd_kafka_topic_conf_set())

[edenhill]

I just used a lower timeout to avoid having to wait so long for the error

[ghost]

changing the message.timeout.ms value to a lower value.
It works now

On Thu, May 15, 2014 at 2:52 PM, Magnus Edenhill
notifications@github.comwrote:

I just used a lower timeout to avoid having to wait so long for the error

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/118#issuecomment-43205048
.

[edenhill]

Great! So what you were seeing was the message waiting to time out because
of the high default timeout value. You would eventually get the error.
Den 16 maj 2014 08:30 skrev "herc6" notifications@github.com:

changing the message.timeout.ms value to a lower value.
It works now

On Thu, May 15, 2014 at 2:52 PM, Magnus Edenhill
notifications@github.comwrote:

I just used a lower timeout to avoid having to wait so long for the
error

—
Reply to this email directly or view it on GitHub<
https://github.com/edenhill/librdkafka/issues/118#issuecomment-43205048>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/118#issuecomment-43301258
.