You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KafkaJs use a default retry = 5, which is extremely small for any internet intermittent issues. The default settings in Java client / Kafka doc in contrast, use MAX_INT as the default value (and they explained why that is the case / recommended value in production). It would make the configs consistent if KafkaJS could follow the same convention. Especially for teams managing interactions with all kinds of Kafka clients for Enterprise.
Ofc, in the end, this is a decision that has to be made by KafkaJS. But IMHO, it would be great that we could follow a consistent convention across different libs to ease communication and minimize surprises in production environments.
The text was updated successfully, but these errors were encountered:
KafkaJs use a default retry = 5, which is extremely small for any internet intermittent issues. The default settings in Java client / Kafka doc in contrast, use MAX_INT as the default value (and they explained why that is the case / recommended value in production). It would make the configs consistent if KafkaJS could follow the same convention. Especially for teams managing interactions with all kinds of Kafka clients for Enterprise.
Ofc, in the end, this is a decision that has to be made by KafkaJS. But IMHO, it would be great that we could follow a consistent convention across different libs to ease communication and minimize surprises in production environments.
The text was updated successfully, but these errors were encountered: