Update documentation for Kafka Supervisor IdleConfig (#14032)

This commit is contained in:
Tejaswini Bandlamudi 2023-04-05 21:55:39 +05:30 committed by GitHub
parent 319f99db05
commit ccf48245d7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions

View File

@ -87,6 +87,8 @@ This topic contains configuration reference information for the Apache Kafka sup
| `enabled` | If `true`, Kafka supervisor will become idle if there is no data on input stream/topic for some time. | no (default == false) | | `enabled` | If `true`, Kafka supervisor will become idle if there is no data on input stream/topic for some time. | no (default == false) |
| `inactiveAfterMillis` | Supervisor is marked as idle if all existing data has been read from input topic and no new data has been published for `inactiveAfterMillis` milliseconds. | no (default == `600_000`) | | `inactiveAfterMillis` | Supervisor is marked as idle if all existing data has been read from input topic and no new data has been published for `inactiveAfterMillis` milliseconds. | no (default == `600_000`) |
> When the supervisor enters the idle state, no new tasks will be launched subsequent to the completion of the currently executing tasks. This strategy may lead to reduced costs for cluster operators while using topics that get sporadic data.
The following example demonstrates supervisor spec with `lagBased` autoScaler and idle config enabled: The following example demonstrates supervisor spec with `lagBased` autoScaler and idle config enabled:
```json ```json
{ {