Cliff, We try not to patch the old consumer too much since we are adding the new java consumer in 0.9. The new consumer supports callbacks during rebalances and can address the problem in KAFKA-2725 better.
Thanks, Jun On Mon, Nov 2, 2015 at 11:16 AM, Cliff Rhyne <crh...@signal.co> wrote: > Hi Jun, > > I openned KAFKA-2725 based on my experience with duplicate message > processing with auto-commit off. I think it's a fairly small change, > especially for someone familiar with the kafka code-base but it makes a big > impact for clients not using auto-commit. Can this be included in 0.9.0? > > Thanks, > Cliff > > On Mon, Nov 2, 2015 at 12:57 PM, Jason Gustafson <ja...@confluent.io> > wrote: > > > I added KAFKA-2691 as well, which improves client handling of > authorization > > errors. > > > > -Jason > > > > On Mon, Nov 2, 2015 at 10:25 AM, Becket Qin <becket....@gmail.com> > wrote: > > > > > Hi Jun, > > > > > > I added KAFKA-2722 as a blocker for 0.9. It fixes the ISR propagation > > > scalability issue we saw. > > > > > > Thanks, > > > > > > Jiangjie (Becket) Qin > > > > > > On Mon, Nov 2, 2015 at 9:16 AM, Jun Rao <j...@confluent.io> wrote: > > > > > > > Hi, everyone, > > > > > > > > We are getting close to the 0.9.0 release. The current plan is to > have > > > the > > > > following remaining 0.9.0 blocker issues resolved this week, cut the > > > 0.9.0 > > > > release branch by Nov. 6 (Friday) and start the RC on Nov. 9 > (Monday). > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%200.9.0.0%20ORDER%20BY%20updated%20DESC > > > > > > > > Thanks, > > > > > > > > Jun > > > > > > > > > > > > > -- > Cliff Rhyne > Software Engineering Lead > m: 760-917-7823 > e: crh...@signal.co > signal.co > ________________________ > > Cut Through the Noise > > This e-mail and any files transmitted with it are for the sole use of the > intended recipient(s) and may contain confidential and privileged > information. Any unauthorized use of this email is strictly prohibited. > ©2015 Signal. All rights reserved. >
