[jira] [Assigned] (KAFKA-8503) AdminClient should ignore retries config if a custom timeout is provided

["huxihx (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

huxihx reassigned KAFKA-8503:
-----------------------------

    Assignee: huxihx

> AdminClient should ignore retries config if a custom timeout is provided
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-8503
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8503
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Assignee: huxihx
>            Priority: Major
>
> The admin client takes a `retries` config similar to the producer. The default value is 5. Individual APIs also accept an optional timeout, which is defaulted to `request.timeout.ms`. The call will fail if either `retries` or the API timeout is exceeded. This is not very intuitive. I think a user would expect to wait if they provided a timeout and the operation cannot be completed. In general, timeouts are much easier for users to work with and reason about.
> A couple options are either to ignore `retries` in this case or to increase the default value of `retries` to something large and not likely to be exceeded. I propose to do the first. Longer term, we could consider deprecating `retries` and avoiding the overloading of `request.timeout.ms` by providing a `default.api.timeout.ms` similar to the consumer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)