Re: [VOTE] SEP-26: Add SystemProducer for Azure Blob Storage

2020-01-08 Thread Prateek Maheshwari
+1 (binding). Thanks for the contribution. - Prateek On Tue, Jan 7, 2020 at 7:59 PM Jagadish Venkatraman wrote: > +1 (binding), looking forward to Samza's integration with Azure blobs > > On Wednesday, January 8, 2020, Lakshmi Manasa > wrote: > > > Hi, > > > > This is a call for a vote on

Re: Reduce kafka partition for a topic samza is using

2020-01-08 Thread Bharath Kumara Subramanian
There are few ways to achieve data copy. 1. Use the vanilla Kafka consumer that consumes data from the old topic and produce to the new topic with fewer partitions. 2. Write a Samza job that reads from your old topic and funnels the data to the new topic. I'd recommend you to follow up with

Re: Problem: upgrade 1.2 to 1.3 caused loss of clean shutdown on SIGTERM

2020-01-08 Thread Thunder Stumpges
Thanks Abhishek, I believe you are correct; removing the shutdown hook from inside the container was the problem. I took the shutdown hook code removed from SamzaContainer in your commit #83e152904ef5 and pulled it out to our App Runner, calling LocalApplicationRunner.kill() and then

Re: Problem: upgrade 1.2 to 1.3 caused loss of clean shutdown on SIGTERM

2020-01-08 Thread Thunder Stumpges
Two things we have done here. When troubleshooting the shutdown deadlock issue, we ran the app in docker container with remote debugging and I could step through all of the Samza (and our) related shutdown code. After the upgrade, none of the breakpoints are hit. Not even our own shutdownHook nor