geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Schuchardt (JIRA)" <>
Subject [jira] [Resolved] (GEODE-1393) locator returns incorrect server information when starting up
Date Mon, 16 May 2016 15:17:12 GMT


Bruce Schuchardt resolved GEODE-1393.
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating.M3

> locator returns incorrect server information when starting up
> -------------------------------------------------------------
>                 Key: GEODE-1393
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: locator
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>             Fix For: 1.0.0-incubating.M3
> When starting up a locator has no knowledge of cache servers that might be in the distributed
system but it will process server-location requests from clients and return them incorrect
information until it receives load info from the servers.
> In one test I saw a locator be ejected from the distributed system.  When it auto-reconnected
some cache clients asked it for server locations and, though there were 6 cache servers available
the clients got this exception:
> {noformat}
> com.gemstone.gemfire.cache.client.NoAvailableServersException
>         at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(
>         at com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.getNextOpServerLocation(
>         at com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(
>         at com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(
>         at com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(
>         at com.gemstone.gemfire.cache.client.internal.GetOp.execute(
>         at com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.get(
>         at com.gemstone.gemfire.internal.cache.tx.ClientTXRegionStub.findObject(
>         at com.gemstone.gemfire.internal.cache.TXStateStub.findObject(
>         at com.gemstone.gemfire.internal.cache.TXStateProxyImpl.findObject(
>         at com.gemstone.gemfire.internal.cache.LocalRegion.get(
>         at com.gemstone.gemfire.internal.cache.LocalRegion.get(
>         at com.gemstone.gemfire.internal.cache.LocalRegion.get(
>         at com.gemstone.gemfire.internal.cache.AbstractRegion.get(
> {noformat}
> ServerLocator has a readiness check but it is only testing to see if its DistributedSystem
instance variable has been initialized.  It ought to wait until it has received a server load

This message was sent by Atlassian JIRA

View raw message