added as a check inside the method
> BlockingEnvelopeMap.put(...) - it is better to delay a bit than halt/crash
> the whole consumer due to memory limitation.
>
>
> Rgds,
> Marcelo
>
>
> From: Yi Pan
> To: dev@samza.apache.org; Marcelo Romaniuc
> Sent: Tuesday, January 19, 2
To: dev@samza.apache.org; Marcelo Romaniuc
Sent: Tuesday, January 19, 2016 5:51 AM
Subject: Re: Custom System Consumer filling up memory
Hi, Marcelo,
Sorry to get back to you late. I remember that Jagadish has some
conversation w/ you on the implementation earlier. Did that include some
hin
Hi, Marcelo,
Sorry to get back to you late. I remember that Jagadish has some
conversation w/ you on the implementation earlier. Did that include some
hints to solve this problem as well? Generally, customized system consumers
would need to be responsible for the memory usage in the customized cod
Hi,
I've created a custom System Consumer extending BlockingEnvelopeMap.
All looks good until I reach about 10m messages processed by the StreamTask.
At that point I see a lot of GC going on and the heap dump shows memory is
mostly used by "IncomingMessageEnvelope" and a ConcurrentHashM
