You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Cory Parent (JIRA)" <ji...@apache.org> on 2016/03/14 16:50:33 UTC
[jira] [Created] (IGNITE-2831) Support advertised address for use
with EC2 service discovery
Cory Parent created IGNITE-2831:
-----------------------------------
Summary: Support advertised address for use with EC2 service discovery
Key: IGNITE-2831
URL: https://issues.apache.org/jira/browse/IGNITE-2831
Project: Ignite
Issue Type: Improvement
Reporter: Cory Parent
Priority: Blocker
Currently it is not possible to connect to an Ignite cluster as a client from a non-AWS environment (e.g. local development machine) due to the manner in which Ignite registers instance addresses. I propose that the default behavior (registering the private IP address) should remain, however, the ability to mitigate this issue should be provided via a method to use an advertised address instead. Such a solution is provided by Kafka configuration to resolve this very issue. This would allow us to override the private IP address with a public or Elastic IP, thus allowing connection from non-AWS environments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)