Hello Laven / Eric, I personally cannot think of any more bug fixes than KAFKA-5152 that is trying to solve a relative issue, and we would love to know what did you observe that in 0.11.0.1 this issue still exists: i.e. the first instance is stuck with the rebalance state, as we have moved the restoration process completely out of the rebalance phase in 0.11.0.1. So as Matthias mentioned, if you still saw this issue in 0.11.0.1 it may indicate another issue.
Again, we are super interested to learn your scenario, and see if it is indeed the case. Guozhang On Sat, Nov 4, 2017 at 7:26 AM, Matthias J. Sax <matth...@confluent.io> wrote: > Streams is backward compatible from 0.10.1 on. > > So 1.0.0 does not work with 0.10.0 but 0.10.1, 0.10.2, and 0.11.0. > > Compare: > https://docs.confluent.io/current/streams/upgrade-guide.html#compatibility > > > -Matthias > > On 10/25/17 7:54 AM, Eric Lalonde wrote: > > > >> On Oct 24, 2017, at 8:53 PM, Matthias J. Sax <matth...@confluent.io> > wrote: > >> > >> Might be worth a try with 1.0.0 RC3 -- even if I doubt that much > changes. > >> > >> Can you provide debug logs for your Kafka streams applications as well > >> as brokers? This would help to dig into this. > >> > > > > I searched, but it wasn’t clear to me — would a Kstream 1.0.0 RC3 client > be backwards compatible with a broker from the 0.10.x line? > > > > > > -- -- Guozhang
