Description
In KAFKA-3514, we introduced a new config for allowing users to delay enforcing processing without all input topic partitions to have data. This config's default value is 0, which means that as long as the first fetch does not contains some records for all the partitions it will fall into enforced processing immediately, which is a high risk especially under bootstrap case.
We should consider leveraging on pause / resume to make sure that upon starting, some partition indeed does not have any data before we fall into enforced processing
Attachments
Issue Links
- is related to
-
KAFKA-3514 Stream timestamp computation needs some further thoughts
-
- Resolved
-
-
KAFKA-4113 Allow KTable bootstrap
-
- Resolved
-
-
KAFKA-8478 Poll for more records before forced processing
-
- Resolved
-
- relates to
-
KAFKA-10091 Improve task idling
-
- Resolved
-