Re: Kafka client.id collision

Hi, Sorry. Here are the logs: First attempt: https://pastebin.com/g6z4hEhZ Second attempt: https://pastebin.com/3XwaRstP Regards Davide > On 20 Jul 2017, at 7:02 pm, Prateek Maheshwari wrote: > > Can you share the entire log fi

Re: Kafka client.id collision

+1 for adding system name to the client id. - Prateek On Thu, Jul 20, 2017 at 10:43 AM, Navina Ramesh (Apache) wrote: > Hi David, > > I think this is expected to occur as a warning since we spin up all kafka > clients with the same client-id, which is $job.name + $job.id. > > As Jagadish mentio

Re: Kafka client.id collision

Hi David, I think this is expected to occur as a warning since we spin up all kafka clients with the same client-id, which is $job.name + $job.id. As Jagadish mentioned, it will be great if you can provide us the entire log so that we can take a look. As a side note for the samza contributors, I

Re: Kafka client.id collision

Can you 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 wrote: > Hi, > > Thanks for the reply. > > It is a warning, but the application fails. Here is the logging: > > > 017-07-20 10:43:06.349 [main] AppInfoPar

Re: Kafka client.id collision

Hi, Thanks for the reply. It is a warning, but the application fails. Here is the logging: 017-07-20 10:43:06.349 [main] AppInfoParser [INFO] Kafka version : 0.10.1.1 2017-07-20 10:43:06.349 [main] AppInfoParser [INFO] Kafka commitId : f10ef2720b03b247 2017-07-20 10:43:06.351 [main] AppInfoPar

Re: Kafka client.id collision

Hi Davide, Is this logged as an error or as a warning? IIUC, this warning should not fail the job. It may not cause some Mbean sensors / metrics emitted from Kafka to be correctly reported (since, those are reported per-clientId). The job should still continue to run. The entire log file will b