Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Mon, 14 Mar 2016 15:50:33 +0000 (UTC)
From: "Cory Parent (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12949920.1457970629000.8960.1457970633493@Atlassian.JIRA>
In-Reply-To: <JIRA.12949920.1457970629000@Atlassian.JIRA>
References: <JIRA.12949920.1457970629000@Atlassian.JIRA>
 <JIRA.12949920.1457970629809@arcas>
Subject: [jira] [Created] (IGNITE-2831) Support advertised address for use
 with EC2 service discovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)