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

[GitHub] samza pull request #247: SAMZA-1368: make sure new job model will be generat...

GitHub user sborya opened a pull request: https://github.com/apache/samza/pull/247 SAMZA-1368: make sure new job model will be generated in case of barrier timeout. You can merge this pull request into a Git repository by running: $ git pull https://github.com/sborya/samza on

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

[GitHub] samza pull request #246: Samza-1364: Handle ZKExceptions in zkCoordinationUt...

GitHub user shanthoosh opened a pull request: https://github.com/apache/samza/pull/246 Samza-1364: Handle ZKExceptions in zkCoordinationUtils.reset. In some cases LocalAppRunner.waitForFinish indefinitely blocks after LocalApplicationRunner.kill. Last step in LocalAppRunner.kill(str

Re: Samza Meetup

No worries. We would love to meet you in person too. Keep an eye out on the mailing list for the Meetup link. Cheers! Navina On Jul 20, 2017 08:37, "Renato Marroquín Mogrovejo" < renatoj.marroq...@gmail.com> wrote: > Thanks Jagadish and Navina! > I am really interested in attending as I am in th

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

[GitHub] samza pull request #245: SAMZA-1366: ScriptRunner should allow callers to co...

GitHub user jmakes opened a pull request: https://github.com/apache/samza/pull/245 SAMZA-1366: ScriptRunner should allow callers to control the child pr… …ocess environment. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jmak

Re: Samza Meetup

Thanks Jagadish and Navina! I am really interested in attending as I am in the area, it'd be my first in-person Samza meetup :D But unfortunately I don't have anything to present this time :( Renato M. 2017-07-18 23:46 GMT-07:00 Navina Ramesh (Apache) : > Hi Renato, > > We are planning for mid-

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

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