[
https://issues.apache.org/jira/browse/KAFKA-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jangho kwon updated KAFKA-14782:
--------------------------------
Description:
Hello,
I was checking the value related to {{{}delivery.timeout.ms{}}}, and I found a
relevant document here:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-91+Provide+Intuitive+User+Timeouts+in+The+Producer]
In the "Validation" section of the document, it is written as follows:
{quote}This configuration is backwards compatible. Throw ConfigException for
timeouts that don't make sense. (E.g., delivery.timeout.ms < linger.ms +
request.timeout.ms + retry.backoff.ms).
{quote}
However, I noticed that the code does not use the {{retry.backoff.ms}} value
when checking if {{delivery.timeout.ms}} is valid.
If it's not a bug, why was it excluded?
was:
Hello,
I was checking the value related to {{{}delivery.timeout.ms{}}}, and I found a
relevant document here:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-91+Provide+Intuitive+User+Timeouts+in+The+Producer]
In the "Validation" section of the document, it is written as follows:
{quote}This configuration is backwards compatible. Throw ConfigException for
timeouts that don't make sense. (E.g., delivery.timeout.ms < linger.ms +
request.timeout.ms + retry.backoff.ms).
{quote}
However, I noticed that the code does not use the {{retry.backoff.ms}} value
when checking if {{delivery.timeout.ms}} is valid.
I'm curious why this value was excluded. Is it a bug?
> Implementation Details Different from Documentation (delivery.timeout.ms)
> -------------------------------------------------------------------------
>
> Key: KAFKA-14782
> URL: https://issues.apache.org/jira/browse/KAFKA-14782
> Project: Kafka
> Issue Type: Bug
> Components: clients, producer
> Reporter: jangho kwon
> Priority: Trivial
>
> Hello,
> I was checking the value related to {{{}delivery.timeout.ms{}}}, and I found
> a relevant document here:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-91+Provide+Intuitive+User+Timeouts+in+The+Producer]
> In the "Validation" section of the document, it is written as follows:
> {quote}This configuration is backwards compatible. Throw ConfigException for
> timeouts that don't make sense. (E.g., delivery.timeout.ms < linger.ms +
> request.timeout.ms + retry.backoff.ms).
> {quote}
> However, I noticed that the code does not use the {{retry.backoff.ms}} value
> when checking if {{delivery.timeout.ms}} is valid.
> If it's not a bug, why was it excluded?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
