[
https://issues.apache.org/jira/browse/ATLAS-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ding updated ATLAS-2087:
--------------------------------
Attachment: ATLAS-2087.addendum.patch
As pointed out by [~madhan.neethiraj] in his review comments, localhost:21000
is not the same endpoint as <ip>:21000 unless the server is bound to address
"0.0.0.0".
This addendum addresses this issue in the startup script. I've tested the
script with following property settings:
{code}
atlas.server.bind.address=<ip on the machine>
atlas.server.bind.address=0.0.0.0
atlas.server.bind.address=127.0.0.1
{code}
> Allow Atlas server to bind on a specific address
> ------------------------------------------------
>
> Key: ATLAS-2087
> URL: https://issues.apache.org/jira/browse/ATLAS-2087
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 0.8-incubating
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2087.2.patch, ATLAS-2087.addendum.patch,
> ATLAS-2087.patch
>
>
> Atlas server always bind to address "0.0.0.0":
> {code}
> connector.setHost("0.0.0.0");
> {code}
> But in many cases, user want to only run Atlas on a specified IP address
> (e.g. private network).
> The existing property "_atlas.server.bind.address_" should be used:
> {code}
> final String addr = conf.get("atlas.server.bind.address", "0.0.0.0");
> connector.setHost(addr);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)