Re: Kafka client.id collision

share the entire log file if that's okay? The warning should be a > red-herring IMHO. > > On Thu, Jul 20, 2017 at 7:50 AM Davide Simoncelli <mailto:netcelli@gmail.com>> > wrote: > >> Hi, >> >> Thanks for the reply. >> >> It is a war

Re: Kafka client.id collision

Id). > > The job should still continue to run. > > The entire log file will be helpful for further debugging! > > On Thu, Jul 20, 2017 at 3:32 AM, Davide Simoncelli <mailto:netcelli@gmail.com>> > wrote: > >> Hello, >> >> We are running Kafka

Kafka client.id collision

Hello, We are running Kafka 0.10.1.1 in production. Unfortunately the Samza app fails to start because of this bug: https://issues.apache.org/jira/browse/SAMZA-1027 . Even hello-samza on YARN fails to start. Here its the error: javax.management

Re: Memory issue

ntensive computation) " > > When you skip some computation, shouldn't the task be faster ? If that's the > case, I suspect the task processes so fast that the consumer never reaches > the 5 threshold. But I haven't verified it. > > Thanks, > > Yan Fang &

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

Re: Containers stuck in event loop

Hi Yi, Thanks. That is likely the reason. I turned debug on and I noticed a deserialisation error. Regards Davide > On 2 Jun 2015, at 6:52 pm, Yi Pan wrote: > > 608

Containers stuck in event loop

Hello, I have had problems running my Samza application on the cluster. The application starts fine and so the main event loop. As soon I start to send messages to Kafka, Samza doesn’t start the Kafka system consumer (there are no logs that state that). The CPU usage for all containers is about

Re: Samza producer error

the message > to > > the brokers from the command line? > > > > Thanks, > > > > Fang, Yan > > yanfang...@gmail.com > > > > On Tue, May 26, 2015 at 5:49 AM, Davide Simoncelli < > netcelli@gmail.com > > > > > wrote: > >

Samza producer error

Hello, I’m testing my Samza application on a 3 nodes clusters. When the kafka producer thread starts to read incoming messages, it keeps throwing the following message on most of containers: 08:19:06.451 [kafka-producer-network-thread | samza_producer-app-1-1432642687162-2] WARN o.a.kafka.com

Re: Number of partitions

Garry, Thanks for sharing. That was an interesting read! I Have few questions for you. How did you test your needed throughput? Only at Kafka level or with your Samza job as well? Did you measure it with metrics? Thanks Davide > On 21 May 2015, at 8:50 pm, Garry Turkington > wrote: > > Hi,

Re: Logback logger

Thank you for your help. It worked. On 14 May 2015 5:17 pm, "Tommy Becker" wrote: > Sorry for not being clear, I'm saying we include logback.xml in the tasks > *jar* file, not just the Samza job's tarball. > > On 05/14/2015 11:19 AM, Davide Simoncelli wrote: >

Re: Logback logger

k as well and simply include logback.xml in the task's jar file. > > On 05/14/2015 08:48 AM, Davide Simoncelli wrote: > > Hello, > > I’m using logback in a Samza project I’m working on. In the dist.tar.gz > package slf4j-log4j12 is not included. > But logback requir

Logback logger

Hello, I’m using logback in a Samza project I’m working on. In the dist.tar.gz package slf4j-log4j12 is not included. But logback requires the configuration file to be in the class path and the run-class.sh script only includes .*jar packages from lib folder. Do you know how I can sort that issu