Thanks, Fred, for driving this release! Thanks for everyone voted!
Cheers!
-Yi
On Thu, Aug 24, 2017 at 2:44 PM, Fred Haifeng Ji
wrote:
> The vote of 0.13.1 RC0 has been more than 72 hours and we got +1 (binding)
> x 3 and +1 (non-binding) x 3.
>
> Samza 0.13.1 officially
The vote of 0.13.1 RC0 has been more than 72 hours and we got +1 (binding)
x 3 and +1 (non-binding) x 3.
Samza 0.13.1 officially passed the VOTE!
Thanks!
Fred
Hi, all,
We have the upcoming Streams meetup @LinkedIn planned on 9/12. We will talk
about realtime search index and Redfin notification using Samza and Kafka
controller updates: come to learn the details in our next streams meet up @
LinkedIn!
Hi Jagadish,
When samza job is shutdown, “Begin to stop” is printed out in the log
file, but not the log in closeFiles.
Now the problem is not program hang, but the container quit before the
“closeFiles” method executed completely.
Thanks.
Qi Shu
> 在
Is "Begin to close file" printed? Where exactly is your application stalled
? I'd suggest you take a stack dump.
On Wed, Aug 23, 2017 at 11:32 PM, 舒琦 wrote:
> Hi Jagadish,
>
> Below is part of the related code, log “"Begin to stop” is printed
> out.
>
> Thank
Hi Jagadish,
Below is part of the related code, log “"Begin to stop” is printed out.
Thank you!
public abstract class MyProducer implements SystemProducer {
@Override
public void stop() {
LOGGER.info("Begin to stop");
closeFiles();
Hi Qi,
>> the stop method in SystemProducer is called, but the close files
operation(may need some time, there may be cache data to be flushed) in
stop method is not executed completely
Are you seeing the *close()* method hang? SystemProducer.*close* is a
synchronous operation, and will block
Hi,
I write a SystemProducer for HDFS and everything is fine. When samza
job is shutdown, the stop method in SystemProducer is called, but the close
files operation(may need some time, there may be cache data to be flushed) in
stop method is not executed completely.
How can I