[
https://issues.apache.org/jira/browse/SAMZA-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kleppmann closed SAMZA-154.
----------------------------------
> hello-samza run-job.sh hangs indefinitely
> -----------------------------------------
>
> Key: SAMZA-154
> URL: https://issues.apache.org/jira/browse/SAMZA-154
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Martin Kleppmann
> Fix For: 0.7.0
>
> Attachments: SAMZA-154.patch
>
>
> While testing SAMZA-153, I discovered that I was unable to get it working
> after this commit:
> https://github.com/linkedin/hello-samza/commit/fc71eb7de9e200960f51e029b898255fd6788f6f
> run-job.sh was just sitting and hanging. Deleting that change from
> yarn-site.xml fixed the problem.
>
> Also, running:
> {noformat}
> export YARN_HOME=.
> {noformat}
> From the root hello-samza directory makes run-job.sh work again. It seems
> like run-job.sh is not picking 127.0.0.1 by default. I assume it's picking
> 0.0.0.0, since that's the default in yarn-default.xml. Forcing YARN_HOME to
> use the same conf for run-job.sh as the RM fixes the problem.
> Not quite sure what the best fix here is. We could make bin/grid export
> YARN_HOME, but if developers open a new shell, they lose the YARN_HOME
> setting, and then their run-job.sh will hang. We can revert the change, but
> [~martinkl] was having problems connecting without this.
> Any other ideas?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
