Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Exit code. The command exits 0 for AVAILABLE. It exits 1 for NOT_STORED, for ERROR, and when the DescribedGroup.ErrorCode is non-zero (authorization failure, group not found, coordinator unavailable, etc.). NOT_REQUESTED does not occur for this command because it always sets IncludeTopologyDescription=true.

Proposed Changes


End-to-end Flow

The sequence below traces the four user-visible interactions — a successful push, a describe, an explicit DeleteGroups, and broker-driven cleanup of a naturally-expired group. Plugin calls return CompletableFutures; the broker awaits them asynchronously.

...

The following broker-side metrics are added under the existing group-coordinator-metrics group (JMX type kafka.server:type=group-coordinator-metrics). Each sensor produces both a rate and a cumulative count.


MBeanTypeDescription
kafka.server:type=group-coordinator-metrics,name=topology-description-plugin-set-success-{rate,count}MeterSuccessful plugin.setTopology calls.
kafka.server:type=group-coordinator-metrics,name=topology-description-plugin-set-error-{rate,count}MeterFailed plugin.setTopology calls. An error increments this sensor regardless of whether it was TopologyDescriptionTooLargeException, InvalidRequestException, or any other exception.
kafka.server:type=group-coordinator-metrics,name=topology-description-plugin-delete-success-{rate,count}MeterSuccessful plugin.deleteTopology calls (covers both the explicit DeleteGroups and periodic-cleanup paths).
kafka.server:type=group-coordinator-metrics,name=topology-description-plugin-delete-error-{rate,count}MeterFailed plugin.deleteTopology calls.
kafka.server:type=group-coordinator-metrics,name=topology-description-plugin-get-success-{rate,count}MeterSuccessful plugin.getTopology calls.
kafka.server:type=group-coordinator-metrics,name=topology-description-plugin-get-error-{rate,count}MeterFailed plugin.getTopology calls.
kafka.server:type=group-coordinator-metrics,name=topology-description-cleanup-cycle-{rate,count}MeterPeriodic topology-description cleanup cycles that actually ran.
kafka.server:type=group-coordinator-metrics,name=topology-description-cleanup-skipped-{rate,count}MeterCycles skipped by the single-flight guard because a prior cycle was still in flight.
kafka.server:type=group-coordinator-metrics,name=topology-description-cleanup-eligible-{rate,count}MeterStreams group IDs identified as eligible for topology-description cleanup, summed across partitions.

No client-side metrics are introduced.

...