You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2014/10/30 22:02:35 UTC
[jira] [Commented] (SAMZA-451) Vagrant hello-samza is broken
[ https://issues.apache.org/jira/browse/SAMZA-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190834#comment-14190834 ]
Yan Fang commented on SAMZA-451:
--------------------------------
Could you try Virtual Box -> Select the VM -> Settings -> Network -> Port Forwarding ? If still not work, + 1 for this ticket.
> Vagrant hello-samza is broken
> -----------------------------
>
> Key: SAMZA-451
> URL: https://issues.apache.org/jira/browse/SAMZA-451
> Project: Samza
> Issue Type: Bug
> Components: hello-samza
> Affects Versions: 0.7.0, 0.8.0
> Reporter: Chris Riccomini
> Assignee: Chris Riccomini
> Fix For: 0.7.0, 0.8.0
>
> Attachments: SAMZA-451-0.patch
>
>
> Two things:
> 1. The bash -x -e command in vagrant/bootstrap.sh didn't work. I had to
> remove the -e switch.
> 2. conf/yarn-site.xml forces YARN to bind to 127.0.0.1. This means that
> 192.168.0.20:8088/cluster/apps doesn't work. Eliminating the
> yarn.resourcemanager.hostname property fixed this.
> Once I did that, I still couldn't contact 192.168.0.20 from my host
> machine. I suspect there's some configuration that needs to be set (or
> removed) to make this work. Given that we don't have any owner for this
> code right now, I'm going to remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)