Re: Memory issue

Hi Davide, Consumer takes the memory is because it maintains a cache for the messages, the size by default is 5. In your case, it maybe as big as 5*12kb. See systems.system-name. samza.fetch.threshold in http://samza.apache.org/learn/documentation/0.9/jobs/configuration-table.html "if

Re: Review Request 33297: [SAMZA-654] Added ElasticsearchSystemProducer and Factory to output messages into Elasticseach indexes.

> On April 17, 2015, 9:49 p.m., Jakob Homan wrote: > > samza-elasticsearch/src/main/java/org/apache/samza/system/elasticsearch/ElasticsearchSystemProducer.java, > > line 97 > > > > > > Can we catch for invalid casts he

Review Request 35115: SAMZA-474 check-all script should fail more gracefully in the absence of gradlew

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35115/ --- Review request for samza. Repository: samza Description --- Improvement

Memory issue

Hello, I have memory issues when running a task on the cluster. The Samza application performs pattern matching on received messages and sends results to another Kafka topic. I tried to put some pressure on the system by sending messages with an average size of 12KiB. After a while containers c