[jira] [Commented] (GEODE-2238) Member may fail to receive cluster configuration from locator

["Dan Smith (JIRA)" <ji...@apache.org>]

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

Dan Smith commented on GEODE-2238:
----------------------------------

Even with my fix to the  changes, I saw GEODE-1976 happen in my precheckin. Looking at the logs, I see the same log message about "No locator(s) found with cluster configuration service."

Digging a little deeper, I think my earlier fix is incomplete. I found this code in StartupMessageReplyProcessor. I think this means that as soon as one member replies to the startup message, we will stop waiting. So we have this same problem where the member startup will continue on and get to GemfireCacheImpl.requestSharedConfiguration before we get the hosted locator information from the StartupResponseWithVersionMessage.

{code}
  /**
   * overridden from ReplyProcessor21 to allow early-out. If an existing member accepted or rejected
   * us then we are done.
   */
  @Override
  protected boolean canStopWaiting() {
    return this.receivedAcceptance || this.receivedRejectionMessage;
  }
{code}

> Member may fail to receive cluster configuration from locator
> -------------------------------------------------------------
>
>                 Key: GEODE-2238
>                 URL: https://issues.apache.org/jira/browse/GEODE-2238
>             Project: Geode
>          Issue Type: Bug
>          Components: management
>    Affects Versions: 1.0.0-incubating
>            Reporter: Kirk Lund
>            Assignee: Dan Smith
>              Labels: Flaky
>
> LuceneClusterConfigurationDUnitTest.indexWithAnalyzerGetsCreatedUsingClusterConfiguration is failing frequently in precheckin. I'm going to mark it as FlakyTest. Below is the stack trace:
> {noformat}
> :geode-lucene:distributedTest
> org.apache.geode.cache.lucene.internal.configuration.LuceneClusterConfigurationDUnitTest > indexWithAnalyzerGetsCreatedUsingClusterConfiguration FAILED
>     org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache.lucene.internal.configuration.LuceneClusterConfigurationDUnitTest$$Lambda$29/613305101.run in VM 2 running on Host 3fb23bc375ef with 4 VMs
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:344)
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:314)
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:259)
>         at org.apache.geode.test.dunit.rules.Member.invoke(Member.java:60)
>         at org.apache.geode.cache.lucene.internal.configuration.LuceneClusterConfigurationDUnitTest.indexWithAnalyzerGetsCreatedUsingClusterConfiguration(LuceneClusterConfigurationDUnitTest.java:102)
>         Caused by:
>         java.lang.AssertionError
>             at org.junit.Assert.fail(Assert.java:86)
>             at org.junit.Assert.assertTrue(Assert.java:41)
>             at org.junit.Assert.assertNotNull(Assert.java:712)
>             at org.junit.Assert.assertNotNull(Assert.java:722)
>             at org.apache.geode.cache.lucene.internal.configuration.LuceneClusterConfigurationDUnitTest.lambda$indexWithAnalyzerGetsCreatedUsingClusterConfiguration$bb17a952$1(LuceneClusterConfigurationDUnitTest.java:105)
> 94 tests completed, 1 failed
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)