[IGNITE-5117] Ignite node in AWS ECS

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.8
• Component/s: zookeeper
• Assignee: Unassigned
• Reporter: vijay c
• Created: 28/Apr/17 19:51
• Updated: 17/Jul/17 08:18

Description

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]