Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-96740

Add retry logic when querying kafka metadata

XMLWordPrintableJSON

    • Atlas Streams
    • Fully Compatible
    • Sprint 65, Sprint 66
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Issue 1: Network error while querying kafka metadata

      A user started a stream processor and ran into:

      Could not connect to the Kafka topic: Local: Broker transport failure (-195)  

      A few minutes later they retried and the processor was able to successfully connect.

      We should add retry logic in our code that calls RdKafka::metadata API.

       

      Issue 2: Network error while querying kafka committed offsets

       Failed to start stream processor: KafkaConsumerOperator failed to get committed offsets: Local: Timed out (-185)

      We should use a longer timeout or add retry logic on our side.

       

            Assignee:
            mayuresh.kulkarni@mongodb.com Mayuresh Kulkarni
            Reporter:
            matthew.normyle@mongodb.com Matthew Normyle
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None