You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/09/11 16:04:00 UTC
[jira] [Updated] (GEODE-5731) --hostname-for-client not working
correclty
[ https://issues.apache.org/jira/browse/GEODE-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dick Cavender updated GEODE-5731:
---------------------------------
Fix Version/s: 1.10.0
> --hostname-for-client not working correclty
> -------------------------------------------
>
> Key: GEODE-5731
> URL: https://issues.apache.org/jira/browse/GEODE-5731
> Project: Geode
> Issue Type: Bug
> Components: configuration, locator
> Affects Versions: 1.6.0
> Reporter: Alexander Murmann
> Assignee: Juan José Ramos Cassella
> Priority: Major
> Labels: SmallFeature
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When starting a server cluster on EC2 and --hostname-for-client set for locator and server then the locator does not return the client-bind-address.
> Locator and server were initially started with
> {code:java}
> start locator --name=locator --port=41111 --properties-file=./gemfire.properties --initial-heap=256M --hostname-for-clients=ec2-12-345-678-90.compute-1.amazonaws.com
> start server --name=server1 --server-port=44666 --properties-file=./gemfire.properties --initial-heap=256M --start-rest-api=true --http-service-port=7676
> {code}
> After some debugging the hostname-for-client on the server was also set to be the public IP address.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)