ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vijay c (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-5117) Ignite node in AWS ECS
Date Fri, 28 Apr 2017 19:52:04 GMT
vijay c created IGNITE-5117:
-------------------------------

             Summary: Ignite node in AWS ECS
                 Key: IGNITE-5117
                 URL: https://issues.apache.org/jira/browse/IGNITE-5117
             Project: Ignite
          Issue Type: Bug
          Components: ignite-zookeeper
    Affects Versions: 1.8
            Reporter: vijay c
            Priority: Blocker


We are using ignite deployed in aws ecs cluster.  Able to use addressresolver to map host
and container ip and register host ip in zookeeper.  But a cleaner thread registers container
ip address in zookeeper as available node after a short while.   

It causes problems for clients as it tries to connect to this node. See log below.   It registers
X.X.X.X  ip in the cluster which is not accessible externally

[DEBUG][tcp-disco-ip-finder-cleaner-#4%gridServer%][TcpDiscoverySpi] Registered missing addresses
in IP finder: [/X.X.X.X:47500, /0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message