DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Status
Current state: Draft
Discussion thread: here
JIRA: here [Change the link from KAFKA-1 to your own ticket]
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
KIP-932: Queues for Kafka introduced share groups to Apache Kafka. This KIP introduces additional group configurations to give users more control over share groups.
Proposed Changes
Some of the configuration for share groups in KIP-932 is specified at the broker level without an equivalent group configuration.
First, it enables group configuration for the maximum number of delivery attempts, so error tolerance can be configured for each group. Second, it enables group configuration for the record lock limit per share-partition, so the balance between resource consumption and concurrency can be configured for each group. The defaults for the equivalent broker configurations were chosen to be suitable for most situations, but group overrides give administrators more control if they desire.
Finally, KIP-1222: Acquisition lock timeout renewal in share consumer explicit mode introduced renewal of acquisition locks. This enables processing of records to be extended indefinitely by repeatedly renewing the acquisition locks. A new group configuration is added to control whether this behavior is permitted for the group. If the value of the configuration is set to false, a renew acknowledgement will be rejected with error code INVALID_RECORD_STATE and an error message which explains that renewing acquisition locks is not enabled for the group.
Public Interfaces
Configuration
Broker configuration
New configurations are added to specify the upper and lower bounds of the associated group configurations.
| Configuration | Description | Values |
|---|---|---|
| (Existing configuration) | Default 5, minimum 2, maximum 10 (no change) |
| The maximum value of a group configuration for the maximum number of delivery attempts for a record delivered to a share group. | Default 10, minimum 5, maximum 25 |
| The minimum value of a group configuration for the maximum number of delivery attempts for a record delivered to a share group. | Default 2, minimum 2, maximum 5 |
| (Existing configuration) | Default 2000, minimum 100, maximum 10000 (no change) |
| The maximum value of a group configuration for the share-group record lock limit per share-partition. | Default 4000, minimum 2000, maximum 10000 |
group.share.min.partition.max.record.locks | The minimum value of a group configuration for the share-group record lock limit per share-partition. | Default 100, minimum 100, maximum 2000 |
Group configuration
| Configuration | Description | Values |
|---|---|---|
share.delivery.count.limit | The maximum number of delivery attempts for a record delivered to the share group. | If not specified, uses the broker configuration If specified, minimum limited by the broker configuration |
share.partition.max.record.locks | Record lock limit per share-partition. | If not specified, uses the broker configuration If specified, minimum limited by the broker configuration |
share.renew.acknowledge.enable | Whether the renew acknowledge type is enabled for the share group. | Valid values "true" (default) and "false" |
Compatibility, Deprecation, and Migration Plan
The changes in this KIP are limited to adding a few new configurations to control existing behavior. There should be no compatibility concerns.
Test Plan
The feature will be thoroughly tested with unit and integration tests.
Rejected Alternatives
None so far.