Thanks Bharath for replying.
Samza job is stateless and running in YARN cluster.
If I follow the below approach.
1. Create a temp kafka topic
2. Copy the messages from old topic to the new topic
3. Delete old topic
4. Create new topic with required partitions
5. Delete old topic
Hi,
This is a call for a vote on SEP-26: Add SystemProducer for Azure Blob
Storage.
Thanks for taking a look and giving feedback.
I have addressed the comments on the SEP and since there were no major
questions/objections, starting this vote.
Discussion thread:
http://mail-archives.apache.org/mo
Hey Thunder,
Thanks for reporting. Taking a look into this and will get back to you when I
have something.
Brett
From: Thunder Stumpges
Sent: Monday, January 6, 2020 6:54 PM
To: dev@samza.apache.org
Subject: Problem: upgrade 1.2 to 1.3 caused loss of clean shut
Thunder,
How were you able to determine that the shutdown hooks are not being called?
If you're able to share any of your shutdown logs from before and after your
1.3 upgrade, that would be helpful while I try to reproduce this issue myself.
Brett
From: Brett Ko
The rational behind moving the shutdown handler out of SamzaContainer was
to let standalone jobs (which are usually part of other online
applications) maintain their own shutdown hooks.
This prevents Samza hooks from running in parallel or causing a deadlock
with the shutdown hooks of parent applic
+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 SEP-26: Add SystemProducer for Azure Blob
> Storage.
> Thanks for taking a look and giving feedback.
>
> I have addressed the comments
