You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "David Harvey (JIRA)" <ji...@apache.org> on 2018/12/21 15:29:00 UTC
[jira] [Commented] (IGNITE-10791) Avoid unusable network during
discovery
[ https://issues.apache.org/jira/browse/IGNITE-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726837#comment-16726837 ]
David Harvey commented on IGNITE-10791:
---------------------------------------
Proposed solution is to allow configuration of TcpCommunicationSpi with a list of regex to exclude addresses that match the pattern. This would allow Ignite to ignite individual IPs or ranges of them, including VPCs. We would still push the addresses that cannot work to the S3 discovery bucket, but other nodes would ignore them.
> 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)