Skip to content

confluentinc#71: Health-checks #126

Open

Description

@astubbs

Mirror of confluentinc/parallel-consumer#71
Opened by JorgenRingen, 2021-01-20 · 3 comments upstream · last upstream activity 2022-11-01
Summarised, not copied. Discussion belongs here - the Confluent-hosted repository is no
longer maintained and may be archived.

Summary

Kafka Streams exposes KafkaStreams#state, which the reporter uses for health checks: healthy while created/rebalancing/running, otherwise restart the app. In PC they had to approximate it with isClosedOrFailed() == false, and ask whether a purpose-built health-check abstraction belongs on the ParallelConsumer interface.

Fork status

Not started. There is no health-check API in the codebase - no HealthCheck type, no
isHealthy(). The approximation in the report, isClosedOrFailed(), is still the only option.

Adjacent: PC exposes Micrometer metrics (see #125), so a liveness signal can be built from those
today, but that is not the purpose-built abstraction this issue asks for.

Unmerged work

confluentinc/parallel-consumer#464 - Feature: Health check and metrics.

Closed unmerged, but not rejected: around 40 of the 53 open PRs were closed on a single day, 2023-06-15, when the maintainer left Confluent. That was an administrative sweep, not a review outcome. The fork's src/docs/development/upstream-pr-analysis.adoc catalogues them as revival candidates.

Ranked A1 - the top revival candidate in the fork's analysis. So this is not a blank sheet: there is an implementation to start from, and it pairs with the metrics work that later shipped separately (#125).

Activity

  1. added
    featureNew capability or improvement to an existing one
    upstream-mirrorMirrored from the upstream confluentinc tracker
    pr-availableAn implementation exists in a PR - open here, or orphaned upstream
    next-breaking-releaseTargeted at the next breaking release (API or architecture change)
    on Aug 5, 2026
  2. astubbs commented on Aug 6, 2026

    @astubbs
    OwnerAuthor

    This is the half that did not land.

    confluentinc#464 was written to close both this issue and astubbs#125 (confluentinc#27, Micrometer metrics) - its body references both. But #464 was superseded, and the PR that finally merged, confluentinc#613, shipped metrics only.

    So metrics arrived in 0.5.2.6 and #125 is closed; health-checks did not, and there is no health-check surface anywhere in src/main today. This issue is the genuinely remaining work of the original pair.

    Full map of the four things called "metrics" here: astubbs#125.

  3. changed the title [-]upstream #71: Health-checks[/-] [+]confluentinc#71: Health-checks[/+] on Aug 6, 2026
  4. self-assigned this
    on Aug 7, 2026
  5. astubbs commented on Aug 7, 2026

    @astubbs
    OwnerAuthor

    PR inbound

  6. added 2 commits that reference this issue on Aug 7, 2026
  7. added this to the 0.6.0.0 milestone on Sep 1, 2026
  8. removed
    0.6.0.0Targeted at the 0.6.0.0 release
    on Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/observabilityArea: observabilityfeatureNew capability or improvement to an existing onegood first issueGood for newcomersnext-breaking-releaseTargeted at the next breaking release (API or architecture change)pr-availableAn implementation exists in a PR - open here, or orphaned upstreamupstream-mirrorMirrored from the upstream confluentinc tracker

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions