[
https://issues.apache.org/jira/browse/SAMZA-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006808#comment-15006808
]
Rick Mangi commented on SAMZA-815:
----------------------------------
Hi [~navina], the same code works fine on 0.9.1 with the only configuration
changes being the addition of the new job.coordinator configs. This
configuration also works on my local grid. I wonder if this is related to
SAMZA-798?
I'm in the process of setting up another kafka mirror to test on without any
0.9.1 checkpoints on it.
> CoordinatorStream - Errors in JobRunner
> ---------------------------------------
>
> Key: SAMZA-815
> URL: https://issues.apache.org/jira/browse/SAMZA-815
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.10.0
> Reporter: Rick Mangi
> Priority: Blocker
> Attachments: joboutput.txt, t_key_grouper.properties
>
>
> When starting a job which I have migrated from 0.9.1 I'm getting an error in
> JobRunner. I will attach full log output and configs.
> [yarnmaster01] out: Exception in thread "main"
> org.apache.samza.SamzaException:
> org.apache.kafka.common.errors.TimeoutException: Failed to update metadata
> after 60000 ms.
> [yarnmaster01] out: at
> org.apache.samza.coordinator.stream.CoordinatorStreamSystemProducer.send(CoordinatorStreamSystemProducer.java:115)
> [yarnmaster01] out: at
> org.apache.samza.coordinator.stream.CoordinatorStreamSystemProducer.writeConfig(CoordinatorStreamSystemProducer.java:132)
> [yarnmaster01] out: at
> org.apache.samza.job.JobRunner.run(JobRunner.scala:85)
> [yarnmaster01] out: at
> org.apache.samza.job.JobRunner$.main(JobRunner.scala:43)
> [yarnmaster01] out: at org.apache.samza.job.JobRunner.main(JobRunner.scala)
> [yarnmaster01] out: Caused by:
> org.apache.kafka.common.errors.TimeoutException: Failed to update metadata
> after 60000 ms.
> [yarnmaster01] out:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
