[ https://issues.apache.org/jira/browse/KAFKA-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
A. Sophie Blee-Goldman updated KAFKA-8575: ------------------------------------------ Description: With KIP-429 the suspend/resume of tasks may have minimal gains while adding a lot of complexity and potential bugs. We should consider removing/cleaning it up and going a step further to remove the EAGER protocol from Streams entirely. Plan to remove this in 3.1/4.0, whichever comes after 3.0. This will make 3.0 a bridge release for users upgrading from any version below 2.4, but they will still be able to do so in the usual two rolling bounces. The upgrade path for any {to_version} higher than 3.0 will be # During the first rolling bounce, upgrade the jars to 3.0 and add the UPGRADE_FROM config for whichever version you are upgrading from # During the second rolling bounce, upgrade the jars to the desired {to_version} and remove the UPGRADE_FROM config EAGER will be effectively deprecated in 3.0 but not removed until the next version. was: With KIP-429 the suspend/resume of tasks may have minimal gains while adding a lot of complexity and potential bugs. We should consider removing/cleaning it up. We should also consider removing EAGER rebalancing from Streams entirely, if results indicate that COOPERATIVE displays superior performance. > Investigate removing EAGER protocol & cleaning up task suspension in Streams > rebalancing > ----------------------------------------------------------------------------------------- > > Key: KAFKA-8575 > URL: https://issues.apache.org/jira/browse/KAFKA-8575 > Project: Kafka > Issue Type: Improvement > Components: streams > Affects Versions: 2.4.0 > Reporter: A. Sophie Blee-Goldman > Priority: Blocker > Fix For: 3.1.0 > > > With KIP-429 the suspend/resume of tasks may have minimal gains while adding > a lot of complexity and potential bugs. We should consider removing/cleaning > it up and going a step further to remove the EAGER protocol from Streams > entirely. > Plan to remove this in 3.1/4.0, whichever comes after 3.0. This will make 3.0 > a bridge release for users upgrading from any version below 2.4, but they > will still be able to do so in the usual two rolling bounces. The upgrade > path for any {to_version} higher than 3.0 will be > # During the first rolling bounce, upgrade the jars to 3.0 and add the > UPGRADE_FROM config for whichever version you are upgrading from > # During the second rolling bounce, upgrade the jars to the desired > {to_version} and remove the UPGRADE_FROM config > EAGER will be effectively deprecated in 3.0 but not removed until the next > version. -- This message was sent by Atlassian Jira (v8.3.4#803005)