| 901 | } |
| 902 | |
| 903 | export interface ConsumerGlobalConfig extends GlobalConfig { |
| 904 | /** |
| 905 | * Client group id string. All clients sharing the same group.id belong to the same group. |
| 906 | */ |
| 907 | "group.id"?: string; |
| 908 | |
| 909 | /** |
| 910 | * Enable static group membership. Static group members are able to leave and rejoin a group within the configured `session.timeout.ms` without prompting a group rebalance. This should be used in combination with a larger `session.timeout.ms` to avoid group rebalances caused by transient unavailability (e.g. process restarts). Requires broker version >= 2.3.0. |
| 911 | */ |
| 912 | "group.instance.id"?: string; |
| 913 | |
| 914 | /** |
| 915 | * The name of one or more partition assignment strategies. The elected group leader will use a strategy supported by all members of the group to assign partitions to group members. If there is more than one eligible strategy, preference is determined by the order of this list (strategies earlier in the list have higher priority). Cooperative and non-cooperative (eager)strategies must not be mixed. `partition.assignment.strategy` is not supported for `group.protocol=consumer`. Use `group.remote.assignor` instead. Available strategies: range, roundrobin, cooperative-sticky. |
| 916 | * |
| 917 | * @default range,roundrobin |
| 918 | */ |
| 919 | "partition.assignment.strategy"?: string; |
| 920 | |
| 921 | /** |
| 922 | * Client group session and failure detection timeout. The consumer sends periodic heartbeats (heartbeat.interval.ms) to indicate its liveness to the broker. If no hearts are received by the broker for a group member within the session timeout, the broker will remove the consumer from the group and trigger a rebalance. The allowed range is configured with the **broker** configuration properties `group.min.session.timeout.ms` and `group.max.session.timeout.ms`. `session.timeout.ms` is not supported for `group.protocol=consumer`. It is set with the broker configuration property `group.consumer.session.timeout.ms` by default or can be configured through the AdminClient IncrementalAlterConfigs API. The allowed range is configured with the broker configuration properties `group.consumer.min.session.timeout.ms` and `group.consumer.max.session.timeout.ms`. Also see `max.poll.interval.ms`. |
| 923 | * |
| 924 | * @default 45000 |
| 925 | */ |
| 926 | "session.timeout.ms"?: number; |
| 927 | |
| 928 | /** |
| 929 | * Group session keepalive heartbeat interval. `heartbeat.interval.ms` is not supported for `group.protocol=consumer`. It is set with the broker configuration property `group.consumer.heartbeat.interval.ms` by default or can be configured through the AdminClient IncrementalAlterConfigs API. The allowed range is configured with the broker configuration properties `group.consumer.min.heartbeat.interval.ms` and `group.consumer.max.heartbeat.interval.ms`. |
| 930 | * |
| 931 | * @default 3000 |
| 932 | */ |
| 933 | "heartbeat.interval.ms"?: number; |
| 934 | |
| 935 | /** |
| 936 | * Group protocol type for the `classic` group protocol. NOTE: Currently, the only supported group protocol type is `consumer`. `group.protocol.type` is not supported for `group.protocol=consumer` |
| 937 | * |
| 938 | * @default consumer |
| 939 | */ |
| 940 | "group.protocol.type"?: string; |
| 941 | |
| 942 | /** |
| 943 | * Group protocol to use. Use `classic` for the original protocol and `consumer` for the new protocol introduced in KIP-848. Available protocols: classic or consumer. Default is `classic`, but will change to `consumer` in next releases. |
| 944 | * |
| 945 | * @default classic |
| 946 | */ |
| 947 | "group.protocol"?: 'classic' | 'consumer'; |
| 948 | |
| 949 | /** |
| 950 | * Server side assignor to use. Keep it null to make server select a suitable assignor for the group. Available assignors: uniform or range. Default is null |
| 951 | */ |
| 952 | "group.remote.assignor"?: string; |
| 953 | |
| 954 | /** |
| 955 | * How often to query for the current client group coordinator. If the currently assigned coordinator is down the configured query interval will be divided by ten to more quickly recover in case of coordinator reassignment. |
| 956 | * |
| 957 | * @default 600000 |
| 958 | */ |
| 959 | "coordinator.query.interval.ms"?: number; |
| 960 |
nothing calls this directly
no outgoing calls
no test coverage detected
searching dependent graphs…