[ 
https://issues.apache.org/jira/browse/GEODE-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386190#comment-16386190
 ] 

ASF subversion and git services commented on GEODE-4765:
--------------------------------------------------------

Commit e5025d399c56b1f86e36c37638108d27655886af in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e5025d3 ]

GEODE-4765: Add retries when retrieving cluster config (#1539)

- This helps when a locator is reconnecting to the distributed system and isn't
  fully ready yet.
- During reconnect, pass a fresh cache to the ClusterConfigurationService -
  this fixes the 'DLock destroyed' issue.
- Also fixes GEODE-4730


> Cluster configuration does not respond after locator reconnects to the 
> distributed system
> -----------------------------------------------------------------------------------------
>
>                 Key: GEODE-4765
>                 URL: https://issues.apache.org/jira/browse/GEODE-4765
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>            Reporter: Jens Deppe
>            Assignee: Jens Deppe
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> In the case of a reconnect event, subsequent server requests for the cluster 
> configuration fail with the following error:
> {noformat}
> [info 2018/02/22 11:16:15.345 IST locator <locator request thread[1]> 
> tid=0x94] Received request for configuration  : ConfigurationRequest for 
> groups :
>    cluster[cluster]
> [info 2018/02/22 11:16:15.346 IST locator <locator request thread[1]> 
> tid=0x94] <DLockService@36820b1e named __CLUSTER_CONFIG_LS destroyed=true 
> grantorId=null grantor=null>  has been destroyed
> org.apache.geode.distributed.LockServiceDestroyedException: 
> <DLockService@36820b1e named __CLUSTER_CONFIG_LS destroyed=true 
> grantorId=null grantor=null>  has been destroyed
>         at 
> org.apache.geode.distributed.internal.locks.DLockService.generateLockServiceDestroyedException(DLockService.java:205)
>         at 
> org.apache.geode.distributed.internal.locks.DLockService.checkDestroyed(DLockService.java:194)
>         at 
> org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1242)
>         at 
> org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1236)
>         at 
> org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1231)
>         at 
> org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1227)
>         at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.createConfigurationResponse(ClusterConfigurationService.java:494)
>         at 
> org.apache.geode.management.internal.configuration.handlers.ConfigurationRequestHandler.processRequest(ConfigurationRequestHandler.java:51)
>         at 
> org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1251)
>         at 
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:434)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to