[
https://issues.apache.org/jira/browse/GEODE-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765782#comment-15765782
]
Dan Smith commented on GEODE-2238:
----------------------------------
I was able to reproduce this running the test in my IDE 50 times.
I see this message in the logs. It looks like vm2 didn't think there were any
locators with cluster configuration, so it got no cluster configuration
information.
{noformat}
[vm_2][info 2016/12/20 17:11:48.802 PST <RMI TCP Connection(1)-127.0.0.1>
tid=0x12] No locator(s) found with cluster configuration service
{noformat}
It looks like there is a race in cluster configuration where we can fail to
realize the locator has cluster configuration enabled.
I tracked this down a bit further, and I suspect the problem is this code in
StartupResponseWithVersionMessage. It calls super.process before calling
dm.addHostedLocators. That means that the thread doing cache initialization and
waiting for a response probably gets unblocked by super.process and might get
through the call to GemfireCacheImpl.requestSharedConfiguration before
dm.addHostedLocators is called.
{code}
@Override
protected void process(DistributionManager dm) {
super.process(dm);
if (this.hostedLocators != null) {
dm.addHostedLocators(getSender(), this.hostedLocators,
this.isSharedConfigurationEnabled);
}
if (logger.isDebugEnabled()) {
logger.debug("Received StartupResponseWithVersionMessage from a member
with version: {}",
this.version);
}
}
{code}
> LuceneClusterConfigurationDUnitTest.indexWithAnalyzerGetsCreatedUsingClusterConfiguration
> fails with AssertionError
> -------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-2238
> URL: https://issues.apache.org/jira/browse/GEODE-2238
> Project: Geode
> Issue Type: Bug
> Components: lucene, tests
> Affects Versions: 1.0.0-incubating
> Reporter: Kirk Lund
> 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)
