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

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

Github user pivotal-amurmann commented on a diff in the pull request:

    https://github.com/apache/geode/pull/683#discussion_r131974883
  
    --- Diff: 
geode-core/src/main/java/org/apache/geode/distributed/internal/locks/DLockService.java
 ---
    @@ -74,17 +73,6 @@
       public static final long NOT_GRANTOR_SLEEP = Long
           .getLong(DistributionConfig.GEMFIRE_PREFIX + 
"DLockService.notGrantorSleep", 100).longValue();
     
    -  public static final boolean DEBUG_DISALLOW_NOT_HOLDER = Boolean
    -      .getBoolean(DistributionConfig.GEMFIRE_PREFIX + 
"DLockService.debug.disallowNotHolder");
    -
    -  public static final boolean DEBUG_LOCK_REQUEST_LOOP = Boolean
    -      .getBoolean(DistributionConfig.GEMFIRE_PREFIX + 
"DLockService.debug.disallowLockRequestLoop");
    -
    -  public static final int DEBUG_LOCK_REQUEST_LOOP_COUNT = Integer
    -      .getInteger(
    -          DistributionConfig.GEMFIRE_PREFIX + 
"DLockService.debug.disallowLockRequestLoopCount", 20)
    -      .intValue();
    -
       public static final boolean DEBUG_NONGRANTOR_DESTROY_LOOP = Boolean
    --- End diff --
    
    how comes we are keeping this debug harness but not the others?


> OldGen heap usage grows without increase in data size, large number of 
> DLockTokens
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-3314
>                 URL: https://issues.apache.org/jira/browse/GEODE-3314
>             Project: Geode
>          Issue Type: Bug
>          Components: distributed lock service
>            Reporter: Udo Kohlmeyer
>            Assignee: Galen O'Sullivan
>             Fix For: 1.2.1
>
>
> When using Global Replicate regions, the DLockTokens are not correctly 
> cleaned up, causing a memory leak.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to