Bruce Schuchardt created GEODE-4037:
---------------------------------------

             Summary: hot loop in persistence advisor consuming CPU and 
producing lots of log output
                 Key: GEODE-4037
                 URL: https://issues.apache.org/jira/browse/GEODE-4037
             Project: Geode
          Issue Type: Bug
          Components: persistence
            Reporter: Bruce Schuchardt


While debugging a test failure I noticed that this code in 
PersistenceAdvisorImpl was causing a hot retry loop that wrote a great deal of 
output to the log file.

{code}
          // Fix for 51698 - If there are online members that we previously
          // failed to get a GII from, retry those members rather than wait
          // for new persistent members to recover.
          if (previousAdvice != null && 
!previousAdvice.getReplicates().isEmpty()) {
            logger.info(
                
LocalizedMessage.create(LocalizedStrings.PersistenceAdvisorImpl_RETRYING_GII));
            previousAdvice = null;
            continue;
          }
{code}

I was going through a lot of tests at the time and didn't note which test hit 
this but I _think_ it was PersistentPartitionedRegionDUnitTest.



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

Reply via email to