Re: Samza yarn job - cannot bind to local host

2016-08-10 Thread Jacob Maes
Hey Shekar, Yes, https://issues.apache.org/jira/browse/SAMZA-825 seems to fit the bill. It hasn't been high priority because most users run samza in YARN or some other multi-tenant environment s.t. the ephemeral ports are ideal. However with the upcoming standalone support, this makes more

Re: Samza yarn job - cannot bind to local host

2016-08-10 Thread Shekar Tippur
Just following on the same thread, is there a feature/bug to force the jmxrmi port? This would be helpful to get the container metrics. - Shekar On Sat, Aug 6, 2016 at 6:14 PM, Shekar Tippur wrote: > Thanks a lot guys. It was a system problem. /etc/hosts file had wrong >

Re: Samza yarn job - cannot bind to local host

2016-08-06 Thread Shekar Tippur
Thanks a lot guys. It was a system problem. /etc/hosts file had wrong permissions. localhost was being resolved to a weird ip for certain users via DNS. - Shekar On Fri, Aug 5, 2016 at 11:27 AM, Jacob Maes wrote: > Hey Shekar, > > There's currently no way to force the port

Re: Samza yarn job - cannot bind to local host

2016-08-05 Thread Jacob Maes
Hey Shekar, There's currently no way to force the port or disable the JMXServer. We've seen port conflicts (fixed in 10.1) and connection issues due to VPN but no connection issue for other reasons. While googling that exception, I found a couple cases without clear resolutions, but they were

Re: Samza yarn job - cannot bind to local host

2016-08-05 Thread Shekar Tippur
Any pointers on this please. I am completely blocked. - Shekar On Thu, Aug 4, 2016 at 5:05 PM, Shekar Tippur wrote: > This server is not connected to vpn. > > - Shekar >

Re: Samza yarn job - cannot bind to local host

2016-08-04 Thread Shekar Tippur
This server is not connected to vpn. - Shekar

Re: Samza yarn job - cannot bind to local host

2016-08-04 Thread Jacob Maes
Hey Shekar, Are your YARN hosts connected to a VPN by chance? The only time I've seen problems with the localhost was when I ran unit tests on my Mac while connected to VPN. Apparently, its related to a bug in Java http://bugs.java.com/view_bug.do?bug_id=7180557 -Jake On Thu, Aug 4, 2016 at

Re: Samza yarn job - cannot bind to local host

2016-08-04 Thread Shekar Tippur
Yi, I can do a curl or telnet to localhost but it is hard to simulate as it spawns random ports. The job fails. Here is the application log: 2016-08-04 20:40:56 SamzaAppMaster$ [INFO] got container id: container_1470270235966_0016_02_01 2016-08-04 20:40:56 SamzaAppMaster$ [INFO] got app

Re: Samza yarn job - cannot bind to local host

2016-08-04 Thread Yi Pan
Hi, Shekar, Please see my replies below: On Thu, Aug 4, 2016 at 12:18 PM, Shekar Tippur wrote: > Sorry .. got trigger happy. > Couple of observations: > 1. rmi port seem to be random ones Even with task.opts and setting the port > to 1099 > You are right. Samza containers

Re: Samza yarn job - cannot bind to local host

2016-08-04 Thread Shekar Tippur
Sorry .. got trigger happy. Couple of observations: 1. rmi port seem to be random ones Even with task.opts and setting the port to 1099 2. Do I need to start rmiregistry manually? 3. I dont have any firewall settings. On Thu, Aug 4, 2016 at 12:14 PM, Shekar Tippur wrote: > Yi

Re: Samza yarn job - cannot bind to local host

2016-08-04 Thread Shekar Tippur
Yi Thanks for responding.. I have tried diff options for task.opts and without it as well. I have tried this task.opts=-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

Re: Samza yarn job - cannot bind to local host

2016-08-04 Thread Yi Pan
Hi, Shekar, Did you check your firewall configuration? Could you also paste your configuration, especially task.opts? -Yi On Wed, Aug 3, 2016 at 5:56 PM, Shekar Tippur wrote: > I am trying to submit a Samza job to yarn and I get a error: > > Exception in thread "main"

Samza yarn job - cannot bind to local host

2016-08-03 Thread Shekar Tippur
I am trying to submit a Samza job to yarn and I get a error: Exception in thread "main" java.io.IOException: Cannot bind to URL [rmi://localhost:44960/jmxrmi]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested