[
https://issues.apache.org/jira/browse/IGNITE-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5117:
------------------------------------
Priority: Major (was: Blocker)
> Ignite node in AWS ECS
> ----------------------
>
> Key: IGNITE-5117
> URL: https://issues.apache.org/jira/browse/IGNITE-5117
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
> Affects Versions: 1.8
> Reporter: vijay c
>
> 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.4.14#64029)
