1st problem is two locators starting up but not seeing each other. I recommend solving this issue first. I'm not aware of any bugs but maybe someone else recognizes this?
2nd problem is probably GEODE-2238. The cause of GEODE-2238 is the Locator starts an asynchronous thread to initialize cluster config. That thread may not have completed initializing cluster config before requests from new Servers start coming in to get the config. Workaround is to delay starting the Servers until the Locator has completed initializing cluster config. On Thu, May 25, 2017 at 6:06 AM, Anton Mironenko <amirone...@amdocs.com> wrote: > Hi Aravind, > Why did you miss the locator property > > --enable-cluster-configuration=true \ > ? > > Anton Mironenko > Software Architect > Amdocs ASP team > > -----Original Message----- > From: Aravind Musigumpula > Sent: Thursday, May 25, 2017 10:54 > To: dev@geode.apache.org > Subject: RE: Geode Exception: cluster configuration service not available > > Hi, > Currently I am using the following configuration : > > locator-specific-props:(used by both locators) > --J=-Dgemfire.jmx-manager=true > --J=-Dgemfire.jmx-manager-start=true > --J=-Dgemfire.jmx-manager-port=(portno.) > --J=-Dgemfire.jmx-manager-http-port=(portno.) > locator-common-props:( used by both locators) > --initial-heap=256M --max-heap=256M > --mcast-port=0 > --locators=address(port), address(port) > --dir=. > --J=-XX:+UseParNewGC --J=-XX:+UseConcMarkSweepGC --J=-XX: > CMSInitiatingOccupancyFraction=60 --J=-XX:+UseCMSInitiatingOccupancyOnly > --J=-XX:+CMSParallelRemarkEnabled -- J=XX:+DisableExplicitGC > --J=-XX:+CMSClassUnloadingEnabled > --J=-verbose:gc --J=-Xloggc:locator-gc.log --J=-XX:+PrintGCDateStamps > --J=-XX:+PrintGCDetails --J=-XX:+PrintTenuringDistribution - J=-XX:+ > PrintGCApplicationConcurrentTime --J=-XX:+PrintGCApplicationStoppedTime > server-common-props(used by both servers) > locators= address(port), address(port) > cache-xml-file=./Server.xml > -J-Dgemfire.ALLOW_PERSISTENT_TRANSACTIONS=true > enable-network-partition-detection=true > disable-auto-reconnect=true > statistic-archive-file=statistics.log > server-specific-props-1(used by both servers) > jmx-manager=false > jmx-manager-start=false > server-jvm-props(used by both servers) > -J-Xmx256M -J-Xms256M > -J-XX:+UseParNewGC -J-XX:+UseConcMarkSweepGC -J-XX: > CMSInitiatingOccupancyFraction=60 -J-XX:+UseCMSInitiatingOccupancyOnly > -J-XX:+CMSParallelRemarkEnabled -J- > XX:+DisableExplicitGC -J-XX:+CMSClassUnloadingEnabled -J-verbose:gc > -J-Xloggc:server-gc.log -J-XX:+PrintGCDateStamps -J-XX:+PrintGCDetails > -J-XX:+PrintTenuringDistribution -J- XX:+ > PrintGCApplicationConcurrentTime -J-XX:+PrintGCApplicationStoppedTime > > Initially it was set to true as it was not working I set it to false and > tried, but it also didn’t work. > > > > Thanks, > Aravind Musigumpula > > -----Original Message----- > From: Jinmei Liao [mailto:jil...@pivotal.io] > Sent: Wednesday, May 24, 2017 8:58 PM > To: dev@geode.apache.org > Subject: Re: Geode Exception: cluster configuration service not available > > Aravind, can you provide us with your startup script and the relevant > locator/server properties file? Is there any reason you want to set the > server's "disable-auto-reconnect" to false? > > On Wed, May 24, 2017 at 4:41 AM, Aravind Musigumpula < > aravind.musigump...@amdocs.com> wrote: > > > > > Hi, > > > > I am using a cluster configuration in geode 1.1.1 . I am starting two > > locators on different hosts and one server for each locator. When I > > stop them and restart the cluster, I can see that in one of the > > locator view , it is receiving only one locator. In gfsh list members, > > I can see only one locator of that host but no server and no other > locator and its server. > > > > I tried enabling the following parameters: > > In locator-specific-props: I have set "enable-cluster-configuration= > true" > > In sever-common-props: I have set "disable-auto-reconnect=false" , > > "use-cluster-configuration=true" > > > > In Server cache log, I am getting an exception : > > Cache server error > > org.apache.geode.GemFireConfigException: cluster configuration service > > not available > > at org.apache.geode.internal.cache.GemFireCacheImpl. > > requestSharedConfiguration(GemFireCacheImpl.java:1067) > > at org.apache.geode.internal.cache.GemFireCacheImpl. > > initialize(GemFireCacheImpl.java:1200) > > at org.apache.geode.internal.cache.GemFireCacheImpl. > > basicCreate(GemFireCacheImpl.java:798) > > at org.apache.geode.internal.cache.GemFireCacheImpl.create( > > GemFireCacheImpl.java:783) > > at org.apache.geode.cache.CacheFactory.create( > > CacheFactory.java:178) > > at org.apache.geode.cache.CacheFactory.create( > > CacheFactory.java:171) > > at org.apache.geode.internal.cache.CacheServerLauncher. > > createCache(CacheServerLauncher.java:813) > > at org.apache.geode.internal.cache.CacheServerLauncher. > > server(CacheServerLauncher.java:657) > > at org.apache.geode.internal.cache.CacheServerLauncher. > > main(CacheServerLauncher.java:201) > > Caused by: org.apache.geode.internal.process. > > ClusterConfigurationNotAvailableException: Unable to retrieve cluster > > configuration from the locator. > > at org.apache.geode.internal.cache.ClusterConfigurationLoader. > > requestConfigurationFromLocators(ClusterConfigurationLoader.java:245) > > at org.apache.geode.internal.cache.GemFireCacheImpl. > > requestSharedConfiguration(GemFireCacheImpl.java:1029) > > ... 8 more > > VM is exiting - shutting down distributed system In one of the locator > > log, I can see this: > > Region /_ConfigurationRegion has potentially stale data. It is waiting > > for another member to recover the latest data. > > . > > . > > . > > > > <Geode Membership View Creator> tid=0x39] View Creator is processing 2 > > requests for the next membership view > > > > received new view: View ... members: .. shutdown: ... > > old view is: View... members... > > Peer locator received new membership view: View.... members: ... > > shutdown: ... > > <Geode Membership View Creator> tid=0x39] no recipients for new view > > aside from myself > > > > > > This seems to be solved in geode 1.1.1 . https://issues.apache.org/ > > jira/browse/GEODE-1986 > > Can anybody help me with this issue. > > > > > > Thanks, > > Aravind > > > > This message and the information contained herein is proprietary and > > confidential and subject to the Amdocs policy statement, > > > > you may review at https://www.amdocs.com/about/email-disclaimer < > > https://www.amdocs.com/about/email-disclaimer> > > > > > > -- > Cheers > > Jinmei > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer < > https://www.amdocs.com/about/email-disclaimer> > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer < > https://www.amdocs.com/about/email-disclaimer> >
