Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-9621

AdminClient listOffsets operation does not respect retries and backoff

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • admin
    • None

    Description

      Similar to https://issues.apache.org/jira/browse/KAFKA-9047, currently the listOffsets operation doesn't respect the configured retries and backoff for a given call. 

      For example, the code path could go like so:
      1) Make a metadata request and schedule subsequent list offsets calls
      2) Metadata error comes back with InvalidMetadataException

      3) Go back to 1

      The problem here is that the state is not preserved across calls. We loose the information regarding how many tries the call has been tried and how far out we should schedule the call to try again. This could lead to a tight retry loop and put pressure on the brokers.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            d8tltanc Cheng Tan
            skaundinya Sanjana Kaundinya

            Dates

              Created:
              Updated:

              Slack

                Issue deployment