Remember when you set 5 with retry.. the order can't be guarantee unless you're producer set as idompotent props as true.. if not you should set 1 to have synchronous call
let's say example, I have 3 brokers, created topic with 3 replication and partition and also my ISR is set to 3. What will happen if one broker goes down, will producer able to send messages to topic as ISR is being followed by 3
with "acks = all" and "min.insync.replicas" is set to 3, you can guarantee that your producer will send that message when you have 3 available brokers. but i believe you usually want more than your min.insync.replicas setting.
Finally you got the title right
i found 6:40 to be particularly useful, explaining in detail what the max flights setting was for.
Thanks 😊
Remember when you set 5 with retry.. the order can't be guarantee unless you're producer set as idompotent props as true.. if not you should set 1 to have synchronous call
@@jcrshankar this is wrong. Since 1.0.0 at least
Thanks very much for such useful information
Happy to help :)
Helpful, thanks :)
Glad it helped!
Good
Is there a similar video for consumer?
Yes please check in the playlist :)
Can you show how you apply it to the previous program?
could you explain kafka broker configuration and consumer configuration
Please checkout complete playlist :)
let's say example, I have 3 brokers, created topic with 3 replication and partition and also my ISR is set to 3. What will happen if one broker goes down, will producer able to send messages to topic as ISR is being followed by 3
with "acks = all" and "min.insync.replicas" is set to 3, you can guarantee that your producer will send that message when you have 3 available brokers. but i believe you usually want more than your min.insync.replicas setting.
Thanks for the video...
Could you pls explain Request.timeout.ms and how it is different from delivery.timeout.ms