[
https://issues.apache.org/jira/browse/IGNITE-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Harvey updated IGNITE-10791:
----------------------------------
Description:
Problem: In some deployments, there are multiple IP addresses, and S3
discovery tries them in some random order, and times out on the ones that don't
work, slowing down discovery unnecessarily. In many such cases, the set of
unusable address is known by humans, but is not discoverable at runtime. For
example, some IP addresses may be blocked by firewalls. On ECS, the docker
bridge network IPs are visible, but are unusable across nodes.
The node pushing IPs to S3 does not have the enough info to decide which of its
address is valid.
[http://apache-ignite-users.70518.x6.nabble.com/Avoiding-Docker-Bridge-network-when-using-S3-discovery-td24778.html]
was:
Problem: In some deployments, there are multiple IP addresses, and S3
discovery tries them in some random order, and times out on the ones that don't
work, slowing down discovery unnecessarily. In many such cases, the set of
unusable address is known by humans, but is not discoverable at runtime. For
example, some IP addresses may be blocked by firewalls. On ECS, the docker
bridge network IPs are visible, but are unusable across nodes.
http://apache-ignite-users.70518.x6.nabble.com/Avoiding-Docker-Bridge-network-when-using-S3-discovery-td24778.html
> Avoid unusable network during discovery
> -----------------------------------------
>
> Key: IGNITE-10791
> URL: https://issues.apache.org/jira/browse/IGNITE-10791
> Project: Ignite
> Issue Type: Improvement
> Reporter: David Harvey
> Priority: Major
>
> Problem: In some deployments, there are multiple IP addresses, and S3
> discovery tries them in some random order, and times out on the ones that
> don't work, slowing down discovery unnecessarily. In many such cases, the
> set of unusable address is known by humans, but is not discoverable at
> runtime. For example, some IP addresses may be blocked by firewalls. On
> ECS, the docker bridge network IPs are visible, but are unusable across nodes.
> The node pushing IPs to S3 does not have the enough info to decide which of
> its address is valid.
>
> [http://apache-ignite-users.70518.x6.nabble.com/Avoiding-Docker-Bridge-network-when-using-S3-discovery-td24778.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
