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

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

Github user kirklund commented on a diff in the pull request:

    https://github.com/apache/geode/pull/483#discussion_r114674582
  
    --- Diff: 
geode-core/src/test/java/org/apache/geode/cache/client/internal/LocatorTestBase.java
 ---
    @@ -289,6 +289,13 @@ public void run() throws Exception {
         }
       }
     
    +  protected void startBridgeClient(final String group, final String host, 
final int port,
    --- End diff --
    
    +1 to Bruce's suggestion


> Change of locator list request interval
> ---------------------------------------
>
>                 Key: GEODE-2853
>                 URL: https://issues.apache.org/jira/browse/GEODE-2853
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server
>            Reporter: Masaki Yamakawa
>            Priority: Minor
>
> If you connect to a Geode cluster using a locator from the client, the 
> locator list request will be executed at regular intervals in the background 
> thread. I want to tune this interval. I understand that this interval can be 
> changed by the ping-interval of the Pool attribute. However, I think that 
> ping-interval originally sets the ping interval for health check to the cache 
> server. Therefore, it is not possible to change the locator list request 
> interval without changing the health check interval to the cache server. So,I 
> want to add a java system property that can change the locator list request 
> interval.
> The locator list request interval is determined by the following priority 
> order.
>   1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
>   2. ping-interval of the Pool attribute
> In addition, when changing this time, the background thread is activated only 
> when this value is a positive value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to