From issues-return-31648-archive-asf-public=cust-asf.ponee.io@geode.apache.org Thu Feb 22 22:12:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5F4F918064E for ; Thu, 22 Feb 2018 22:12:04 +0100 (CET) Received: (qmail 22256 invoked by uid 500); 22 Feb 2018 21:12:03 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 22247 invoked by uid 99); 22 Feb 2018 21:12:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2018 21:12:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0C1211A02AC for ; Thu, 22 Feb 2018 21:12:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 6nPVvYSaFKhT for ; Thu, 22 Feb 2018 21:12:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 776495F341 for ; Thu, 22 Feb 2018 21:12:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9BB22E01A8 for ; Thu, 22 Feb 2018 21:12:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 56C5827131 for ; Thu, 22 Feb 2018 21:12:00 +0000 (UTC) Date: Thu, 22 Feb 2018 21:12:00 +0000 (UTC) From: "Kyle R Dunn (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (GEODE-4726) Documentation is misleading with a multi-homed Geode cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GEODE-4726?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle R Dunn updated GEODE-4726: ------------------------------- Description:=20 Trying to bind Geode to an arbitrary network interface (e.g. {{eth2}}), req= uires some non-obvious parameters to be set.=C2=A0 Some of these parameters= appear to be unrelated to multi-homing entirely, yet are necessary for bot= h a locator and server to start correctly. For example, the {{server-bind-address=3Dw.x.y.z}} parameter appears to hav= e no effect on the interface used by the server process;=C2=A0 however pass= ing=C2=A0{{bind-address=3Dw.x.y.z}} to the server startup produces the corr= ect startup behavior. Additionally, the {{hostname-for-clients}} parameter appears to be required= for certain Geode extensions to function once added to the {{CLASSPATH}} -= in my case it was a propriety Pivotal extension (GGC).=C2=A0 {code:bash} // The following script was used successfully on Mac OS to bind to the "las= t" interface listed by ifconfig (vmnet8) #!/bin/bash rm -rf locator1 server1 export GEODE_HOME=3D/opt/pivotal-gemfire-9.3.0 export CLASSPATH=3D${GEODE_HOME}/lib/gemfire-greenplum-3.1.1.jar gfsh < Documentation is misleading with a multi-homed Geode cluster > ------------------------------------------------------------ > > Key: GEODE-4726 > URL: https://issues.apache.org/jira/browse/GEODE-4726 > Project: Geode > Issue Type: Bug > Components: configuration > Reporter: Kyle R Dunn > Priority: Major > > Trying to bind Geode to an arbitrary network interface (e.g. {{eth2}}), r= equires some non-obvious parameters to be set.=C2=A0 Some of these paramete= rs appear to be unrelated to multi-homing entirely, yet are necessary for b= oth a locator and server to start correctly. > For example, the {{server-bind-address=3Dw.x.y.z}} parameter appears to h= ave no effect on the interface used by the server process;=C2=A0 however pa= ssing=C2=A0{{bind-address=3Dw.x.y.z}} to the server startup produces the co= rrect startup behavior. > Additionally, the {{hostname-for-clients}} parameter appears to be requir= ed for certain Geode extensions to function once added to the {{CLASSPATH}}= - in my case it was a propriety Pivotal extension (GGC).=C2=A0 > {code:bash} > // The following script was used successfully on Mac OS to bind to the "l= ast" interface listed by ifconfig (vmnet8) > #!/bin/bash > rm -rf locator1 server1 > export GEODE_HOME=3D/opt/pivotal-gemfire-9.3.0 > export CLASSPATH=3D${GEODE_HOME}/lib/gemfire-greenplum-3.1.1.jar > gfsh < start locator --name=3Dlocator1 --locators=3D172.16.139.1[10334] --bind-a= ddress=3D172.16.139.1 --port=3D10334 --include-system-classpath --hostname-= for-clients=3D172.16.139.1 > start server --name=3Dserver1 --start-rest-api=3Dtrue --http-service-port= =3D28080 --locators=3D172.16.139.1[10334] --bind-address=3D172.16.139.1 --= cache-xml-file=3D../config/ggc_cache.xml --classpath=3D${CLASSPATH} --inclu= de-system-classpath > EOF > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)