Hi,
Thanks for all the suggestions.
Finally, after clearing - network DNS caches, restarting the machines,
creating static routes & clearing the hostname file, I was able to create
the setup. Still, I am not sure what is the least required set of
properties, yet.
For all future folks :
*Setup :*
NODE 1 - (192.168.20.100) - Locator & Server1.
NODE 2 - (192.168.20.101) - Server2
*NODE 1:*
*locator.properties*
jmx-manager=true
jmx-manager-bind-address=192.168.20.100
jmx-manager-hostname-for-clients=192.168.20.100
jmx-manager-http-port=7070
jmx-manager-port=1099
jmx-manager-start=true
$> gfsh
*gfsh>start locator --name=locator --properties-file="locator.properties"
--port=10334 --bind-address=192.168.20.100
--hostname-for-clients=192.168.20.100
--J=-Djava.rmi.server.hostname=192.168.20.100*
*gfsh>start server --name=server1 --locators=192.168.20.100[10334]
--bind-address=192.168.20.100 --server-bind-address=192.168.20.100
--hostname-for-clients=192.168.20.100
--J=-Djava.rmi.server.hostname=192.168.20.100*
*gfsh>list members;*
* Name | Id*
*------- | --------------------------------------------------*
*locator | 192.168.20.100(locator:23887:locator)<ec><v0>:1024*
*serve1 | 192.168.20.100(serve1:24136)<ec><v1>:1025*
*NODE 2:*
*gfsh>connect --locator=192.168.20.100[10334]*
*Connecting to Locator at [host=192.168.20.100, port=10334] ..*
*Connecting to Manager at [host=192.168.20.100, port=1099] ..*
*Successfully connected to: [host=192.168.20.100, port=1099]*
*gfsh>start server --name=server2 --locators=192.168.20.100[10334]
--bind-address=192.168.20.101 --server-bind-address=192.168.20.101
--hostname-for-clients=192.168.20.101
--J=-Djava.rmi.server.hostname=192.168.20.101*
gfsh>list members;
Name | Id
------- | --------------------------------------------------
locator | 192.168.20.100(locator:23887:locator)<ec><v0>:1024
server2 | 192.168.20.101(server2:59856)<ec><v2>:1024
server1 | 192.168.20.100(serve1:24136)<ec><v1>:1025
gfsh> SUCCESS !
-------------------------------------------------------------------------------------------
Issue Observation:
I previously had hosts file entries defined for all my static IP addresses.
1. 192.168.20.100 - alps
2. 192.168.20.101 - indus
Whenever I was starting locator & server, JVM resolved IP addresses to
these hostnames automatically.
gfsh>list members;
Name | Id
------- | ----------------------------------------
locator | alps(locator:2924:locator)<ec><v0>:1024
server1 | alps(server1:3157)<ec><v1>:1025
So whenever, I was starting a local server on <NODE 1/alps>, the server
entry was picked up.
*Node 2*
Starting the server2 JGroups never gets any replies for the coordinator
requests, after sometime server2 becomes the leader of its own group.
*Log:*
info 2016/02/14 18:45:47.763 EST server2 <main> tid=0x1] Starting
membership services
[info 2016/02/14 18:45:47.890 EST server2 <main> tid=0x1] JGroups channel
created (took 126ms)
[info 2016/02/14 18:45:47.910 EST server2 <main> tid=0x1] GemFire P2P
Listener started on null
[info 2016/02/14 18:45:47.912 EST server2 <Geode Failure Detection Server
thread 0> tid=0x22] Started failure detection server thread on indus/
192.168.20.101:35322.
[info 2016/02/14 18:45:47.984 EST server2 <main> tid=0x1] Attempting to
join the distributed system through coordinator
indus(locator:2113:locator)<ec><v0>:1024 using address
indus(server2:56742)<ec>:1024
[info 2016/02/14 18:46:01.018 EST server2 <main> tid=0x1] Attempting to
join the distributed system through coordinator
alps(server1:2364)<ec><v1>:1025 using address indus(server2:56742)<ec>:1024
[info 2016/02/14 18:46:14.046 EST server2 <main> tid=0x1] This member is
becoming the membership coordinator with address
indus(server2:56742)<ec>:1024
[info 2016/02/14 18:46:14.047 EST server2 <main> tid=0x1] received new
view: View[indus(server2:56742)<ec><v0>:1024|0] members:
[indus(server2:56742)<ec><v0>:1024{lead}]
old view is: null
[info 2016/02/14 18:46:14.052 EST server2 <Geode Membership View Creator>
tid=0x59] View Creator thread is starting
[info 2016/02/14 18:46:14.053 EST server2 <main> tid=0x1] Finished joining
(took 26139ms).
[info 2016/02/14 18:46:14.054 EST server2 <main> tid=0x1] Starting
DistributionManager indus(server2:56742)<ec><v0>:1024. (took 26417 ms)
[info 2016/02/14 18:46:14.054 EST server2 <main> tid=0x1] Initial
(distribution manager) view = View[indus(server2:56742)<ec><v0>:1024|0]
members: [indus(server2:56742)<ec><v0>:1024{lead}]
[info 2016/02/14 18:46:14.057 EST server2 <main> tid=0x1] Did not hear back
from any other system. I am the first one.
[info 2016/02/14 18:46:15.612 EST server2 <main> tid=0x1] No locator(s)
found with cluster configuration service
[info 2016/02/14 18:46:15.633 EST server2 <main> tid=0x1] Initializing
region PdxTypes
[info 2016/02/14 18:46:15.633 EST server2 <main> tid=0x1] Initialization of
region PdxTypes completed
[info 2016/02/14 18:46:15.653 EST server2 <main> tid=0x1] Cache server
connection listener bound to address /192.168.20.101:55230 with backlog
1,000.
[info 2016/02/14 18:46:15.675 EST server2 <main> tid=0x1]
ClientHealthMonitorThread maximum allowed time between pings: 60,000
Please let me know, if you find this to be the same.
*Feedback - Simple Init Scripts*
I felt, a lot of configuration/settings lookups have to be done for
distributed setup. It may be an issue for folks just starting with Geode. I
prefer the way Cassandra/Elasticsearch projects do it, may be Geode can
also have init-scripts included in the distribution.
*$ sh start-locator.sh <IP_ADDRESS>*
*$ sh start-server.sh <IP_ADDRESS>*
Thanks,
Alan
>>>>
