[jira] [Commented] (KAFKA-7458) Avoid enforced processing during bootstrap phase
[ https://issues.apache.org/jira/browse/KAFKA-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376886#comment-17376886 ] John Roesler commented on KAFKA-7458: - Hello again, all, this issue should be resolved in AK 3.0 by KIP-695 / KAFKA-10091 > Avoid enforced processing during bootstrap phase > > > Key: KAFKA-7458 > URL: https://issues.apache.org/jira/browse/KAFKA-7458 > Project: Kafka > Issue Type: Improvement > Components: streams >Reporter: Guozhang Wang >Assignee: John Roesler >Priority: Major > > 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-7458) Avoid enforced processing during bootstrap phase
[ https://issues.apache.org/jira/browse/KAFKA-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244327#comment-17244327 ] John Roesler commented on KAFKA-7458: - Hello, all, I have just proposed KIP-695, which I think would resolve this issue. Please let me know what you think in the mailing list discussion thread! https://cwiki.apache.org/confluence/x/JSXZCQ > Avoid enforced processing during bootstrap phase > > > Key: KAFKA-7458 > URL: https://issues.apache.org/jira/browse/KAFKA-7458 > Project: Kafka > Issue Type: Improvement > Components: streams >Reporter: Guozhang Wang >Assignee: Guozhang Wang >Priority: Major > > 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-7458) Avoid enforced processing during bootstrap phase
[ https://issues.apache.org/jira/browse/KAFKA-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633951#comment-16633951 ] Antony Stubbs commented on KAFKA-7458: -- Related to KAFKA-4113 > Avoid enforced processing during bootstrap phase > > > Key: KAFKA-7458 > URL: https://issues.apache.org/jira/browse/KAFKA-7458 > Project: Kafka > Issue Type: Improvement > Components: streams >Reporter: Guozhang Wang >Assignee: Guozhang Wang >Priority: Major > > 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
