No errors when produce to non-existent external broker about librdkafka HOT 5 CLOSED

2.2.2.2:9092 is not answering and thus the TCP connectioning is waiting in the CONNECT state waiting for a positive or negative reply from the remote host - but since there is no such host the connection attempt will have to timeout.
If you wait for a couple of minutes I think you will get a timeout error.

from librdkafka.

If request.required.acks != 0 (defaults to 1) the message will eventually timeout and you will get a delivery report.

from librdkafka.

Thank you, but is there any method to wait for connection (for x ms) and then to produce a message?

from librdkafka.

rdkafka tries to remove all that logic from the client.
All the client needs to do is say where the brokers can be reached and then
start producing or consuming messages:
rdkafka will handle everything else; connects, disconnects, errors, etc.
If the broker is not available or takes time to connect to the messages
will be queued locally inside rdkakfa for "message.timeout.ms", eventually
sending the
message when the broker becomes available, or timing out the message when
the timeout is reached.
This async approach provides high throughput and makes the application's
design easier since it does not need check or maintain any state for the
kafka cluster.

What the application may do is register an err_cb to receive error reports
from librdkafka.
Connection failures are reported with error code
RD_KAFKA_RESP_ERR__TRANSPORT.

2014/1/10 Aleksandar Babic [email protected]

Thank you, but is there any method to wait for connection (for x ms) and
then to produce a message?

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

from librdkafka.

Thanks a lot, I learned a lot from you and your code. ;)

from librdkafka.