You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Xinyu Liu (JIRA)" <ji...@apache.org> on 2015/10/23 20:47:27 UTC

[jira] [Created] (SAMZA-799) Local deployment working with using VPN

Xinyu Liu created SAMZA-799:
-------------------------------

             Summary: Local deployment working with using VPN
                 Key: SAMZA-799
                 URL: https://issues.apache.org/jira/browse/SAMZA-799
             Project: Samza
          Issue Type: Improvement
            Reporter: Xinyu Liu
            Priority: Minor


When VPN is used, locally deployed samza job may fail due to a SocketTimeoutException that container tries to connect to the HTTP
server that Samza starts in the JobCoordinator(runs within the AM) to pass
the configs. The reason is that when VPN is activated, it will disable the previous IP address allocated. But when samza retrieves the URL for http server (HttpServer.scala:getUrl), it will get the disabled IP address. So subsequent request will fail to connect to it, resulting failure to load the configs.

A possible solution is to make the local IP address configurable, so users can specify it when VPN is used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)