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

ASF GitHub Bot commented on GEODE-8099:
---------------------------------------

jinmeiliao commented on a change in pull request #5188:
URL: https://github.com/apache/geode/pull/5188#discussion_r437003230



##########
File path: 
geode-core/src/main/java/org/apache/geode/management/internal/api/LocatorClusterManagementService.java
##########
@@ -114,6 +122,7 @@
   private final MemberValidator memberValidator;
   private final CommonConfigurationValidator commonValidator;
   private final InternalCache cache;
+  private DistributedLockService cmsDlockService;

Review comment:
       I tried your approach, but that affects lots of other integration tests 
that uses some API in InternalLocator that would start the cms service and hit 
error when they can't get the dlockservice to inject to it. 

##########
File path: 
geode-core/src/main/java/org/apache/geode/management/internal/api/LocatorClusterManagementService.java
##########
@@ -114,6 +122,7 @@
   private final MemberValidator memberValidator;
   private final CommonConfigurationValidator commonValidator;
   private final InternalCache cache;
+  private DistributedLockService cmsDlockService;

Review comment:
       I tried your approach, but that affects lots of other integration tests 
that uses some API in InternalLocator that would start the cms service and hit 
error when they can't get the dlockservice to inject to it. So I had to revert 
it back




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Make ClusterConfiguration Service thread safe
> ---------------------------------------------
>
>                 Key: GEODE-8099
>                 URL: https://issues.apache.org/jira/browse/GEODE-8099
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>            Reporter: Anilkumar Gingade
>            Priority: Major
>              Labels: GeodeOperationAPI
>             Fix For: 1.14.0
>
>
> When multiple cluster configuration clients (multiple rest clients) connects 
> and issue configuration commands, the cluster configuration should handle 
> concurrent request and modify/save/execute the configuration definition in 
> thread safe manner.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to