[ 
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812569#comment-15812569
 ] 

ASF GitHub Bot commented on FLINK-2821:
---------------------------------------

Github user schmichri commented on the issue:

    https://github.com/apache/flink/pull/2917
  
    short: it works!
    
    long: my scenario a docker-compose setup: 
    
    `  jobmanager:
        image: flink:1.2.0_rc0
        container_name: "jobmanager"
        expose:
          - "6123"
          - "8081"
        ports:
          - "8081:8081"
          - "10.0.0.11:6123:6123"
        command: jobmanager
        environment:
         - JOB_MANAGER_RPC_ADDRESS=10.0.0.11
    `
    and the taskmanager(s):
    `  taskmanager:
        image: flink:1.2.0_rc0
        expose:
          - "6121"
          - "6122"
        command: taskmanager
          - "jobmanager:jobmanager"
        environment:
          - JOB_MANAGER_RPC_ADDRESS=10.0.0.11
        extra_hosts:
          - "jobmanager:10.0.0.11"`
    
    1. the jobmanager webinterface works now
    2. the taskmanager can connect now to the jobmanager 
    previous errormessage: 
    > dropping message [class akka.actor.ActorSelectionMessage] for non-local 
recipient [Actor[akka.tcp://[email protected]:6123/]] arriving at 
[akka.tcp://[email protected]:6123] inbound addresses are 
[akka.tcp://[email protected]:6123]
    > flink-master    | 2017-01-09 15:30:39,865 ERROR akka.remote.EndpointWriter
    
    thats very cool! 


> Change Akka configuration to allow accessing actors from different URLs
> -----------------------------------------------------------------------
>
>                 Key: FLINK-2821
>                 URL: https://issues.apache.org/jira/browse/FLINK-2821
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>            Reporter: Robert Metzger
>            Assignee: Maximilian Michels
>             Fix For: 1.2.0
>
>
> Akka expects the actor's URL to be exactly matching.
> As pointed out here, cases where users were complaining about this: 
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Error-trying-to-access-JM-through-proxy-td3018.html
>   - Proxy routing (as described here, send to the proxy URL, receiver 
> recognizes only original URL)
>   - Using hostname / IP interchangeably does not work (we solved this by 
> always putting IP addresses into URLs, never hostnames)
>   - Binding to multiple interfaces (any local 0.0.0.0) does not work. Still 
> no solution to that (but seems not too much of a restriction)
> I am aware that this is not possible due to Akka, so it is actually not a 
> Flink bug. But I think we should track the resolution of the issue here 
> anyways because its affecting our user's satisfaction.



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

Reply via email to