Hey Shekar, The full list of 0.9.0 features and fixes is here:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20%3D%200.9.0%20AND%20status%20in%20(Resolved%2C%20Closed) Re: SQL and windowing, most of that work has been done in isolation in the samza-sql branch: https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tree;h=refs/heads/samza-sql;hb=refs/heads/samza-sql This branch is periodically rebased with 0.9.0, but has added patches from Milinda, Navina, Yi, etc. Cheers, Chris On Tue, Mar 31, 2015 at 10:46 AM, Shekar Tippur <[email protected]> wrote: > Perfect Chris. We will test out the latest version. Did not get a chance to > test it. > On the same note, as I have not caught up with 0.9.0, is there anyway to > get the feature list or some release notes for 0.9.0. I am interested with > the windowing and SQL like capabilities. > > - Shekar > > On Tue, Mar 31, 2015 at 9:19 AM, Chris Riccomini <[email protected]> > wrote: > > > Hey Shekar, > > > > Are you running with 0.8.0 when you run these tests? If so, there are > some > > known issues where a Samza consumer can get stuck when brokers > disappeared. > > All known issues have been resolved in the 0.9.0 release, but they exist > in > > the 0.8.0 release. > > > > Cheers, > > Chris > > > > On Mon, Mar 30, 2015 at 5:26 PM, Shekar Tippur <[email protected]> > wrote: > > > > > One more thing .. > > > > > > We have this configured as well. > > > > > > > > > > > > systems.kafka.producer.metadata.broker.list=sprfargas102:6667,sprfargas103:6667 > > > > > > On Mon, Mar 30, 2015 at 5:08 PM, Shekar Tippur <[email protected]> > > wrote: > > > > > > > Hello, > > > > > > > > I realise this is a Kafka question. Since there are quite a few Kafka > > > > experts here and the answer to this question can help Samza community > > as > > > > well, bringing this question here. > > > > > > > > We are testing Kafka redundancy (just 2 brokers for now). > > > > > > > > We have increased replication factor to 2 servers (Both kafka > brokers) > > > > We have included auto.leader.rebalance.enable=true so that the leader > > > gets > > > > redundancy and bounced Kafka. > > > > We have moved the topic across both the servers. > > > > > > > > Below table shows the sequence of events. Can someone please explain > > why > > > > we see this behaviour in step 4? > > > > > > > > > > > > > > > > Broker 1 > > > > > > > > Broker 2 > > > > > > > > Kafka status > > > > > > > > Step 1 > > > > > > > > Up > > > > > > > > Up > > > > > > > > Running > > > > > > > > Step 2 > > > > > > > > Down > > > > > > > > Up > > > > > > > > Running > > > > > > > > Step 3 > > > > > > > > Up > > > > > > > > Up > > > > > > > > Running > > > > > > > > Step 4 > > > > > > > > Up > > > > > > > > Down > > > > > > > > Not running (Connection refused) > > > > > > > > > >
