Skip to content

KAFKA-20161 Group configuration for share.renew.acknowledge.enable#21467

Open
DL1231 wants to merge 2 commits intoapache:trunkfrom
DL1231:KAFKA-20037
Open

KAFKA-20161 Group configuration for share.renew.acknowledge.enable#21467
DL1231 wants to merge 2 commits intoapache:trunkfrom
DL1231:KAFKA-20037

Conversation

@DL1231
Copy link
Collaborator

@DL1231 DL1231 commented Feb 13, 2026

Introduce the share.renew.acknowledge.enable group configuration
(KIP-1222) to control whether renew acknowledgements are permitted for a
share group.

  • Add new boolean dynamic group config
    share.renew.acknowledge.enable (default false) in GroupConfig -
    When disabled, RENEW acknowledgements are rejected with
    INVALID_RECORD_STATE error code - Update existing RENEW tests to
    explicitly enable the config - Add unit tests and integration test
    for the disabled-by-default behavior

@github-actions github-actions bot added triage PRs from the community core Kafka Broker KIP-932 Queues for Kafka clients group-coordinator labels Feb 13, 2026
@chia7712 chia7712 changed the title KAFKA-20037: Group configuration for share.renew.acknowledge.enable KAFKA-20161 Group configuration for share.renew.acknowledge.enable Feb 13, 2026
* @param groupId The group id for which the renew acknowledge enable is to be checked.
* @return true if renew acknowledge is enabled for the group, false otherwise.
*/
public static boolean isRenewAcknowledgeEnabled(GroupConfigManager groupConfigManager, String groupId) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we move this to GroupMetadataManager?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving this to GroupMetadataManager would require introducing GroupMetadataManager as a new dependency of SharePartition, which seems like unnecessary coupling. The similar config-accessor methods in
GroupMetadataManager (e.g., consumerGroupSessionTimeoutMs) serve the coordinator's own internal logic, whereas this helper serves the share partition layer.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about GroupConfigManager?

@github-actions github-actions bot removed the triage PRs from the community label Feb 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants