redpanda-data / redpanda-data/connect

Kafka franz returns ready OK even when it can't connect

Open
#2,272 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug ux
Dominant language
Go
Stars
8.8k
Forks
969
Avg merge
1d 13h
Merged PRs (30d)
64

Description

Example code

input: kafka_franz: seed_brokers: [ "localhost:6666" ] topics: [ "foobar" ] consumer_group: "benthos"
ready endpoint returns OK

App dies with sigterm after a few secods

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the kafka_franz configuration with localhost:6666 unavailable and observing the ready endpoint and subsequent SIGTERM. Trace the readiness entry point and Kafka connection handling; done means readiness no longer reports OK when the configured broker cannot be reached, with a regression test for this scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
stream-processing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.