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

New producer/consumer should support configurable connection timeouts

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.8.2.0
    • Fix Version/s: None
    • Component/s: clients, config
    • Labels:
      None

      Description

      During discussion of KAFKA-1642 it became clear that the current connection handling code for the new clients doesn't give enough flexibility in some failure cases. We need to support connection timeouts that are configurable via Kafka configs rather than relying on the underlying TCP stack's default settings. This would give the user control over how aggressively they want to try new servers when trying to fetch metadata (currently dependent on the underlying OS timeouts and some implementation details of NetworkClient.maybeUpdateMetadata and NetworkClient.leastLoadedNode), which is the specific issue that came up in KAFKA-1642. More generally it gives better control over how fast the user sees failures when there are network failures.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ewencp Ewen Cheslack-Postava
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: