geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-1557) LuceneQueriesPeerPRDUnitTest.returnCorrectResultsAfterRebalance fails with suspect string error
Date Thu, 23 Jun 2016 17:26:16 GMT


ASF subversion and git services commented on GEODE-1557:

Commit 83c7c661648c9fd7b0dac054dde60e2ae1ef12cd in incubator-geode's branch refs/heads/feature/GEODE-1573
from [~adharmakkan]
[;h=83c7c66 ]

GEODE-1557: Not logging BucketNotFoundException

Not logging BucketNotFoundException as an error in LuceneEventLister and added
a test shouldIgnoreBucketNotFoundException to verify it

This closes #168

> LuceneQueriesPeerPRDUnitTest.returnCorrectResultsAfterRebalance fails with suspect string
> -----------------------------------------------------------------------------------------------
>                 Key: GEODE-1557
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Aparna Dharmakkan
> This test failed with the following error
> {noformat}
> Suspicious strings were written to the log during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 61460
> [error 2016/06/16 12:02:33.844 PDT <Event Processor for GatewaySender_AsyncEventQueue_index#_region_0>
tid=1453] Unable to save to lucene index
> com.gemstone.gemfire.internal.cache.BucketNotFoundException: User bucket was not found
for region Partitioned Region @149884aa [path='/region'; dataPolicy=PARTITION; prId=92; isDestroyed=false;
isClosed=false; retryTimeout=3600000; serialNumber=10558; partition attributes=PartitionAttributes@1660363202[redundantCopies=0;localMaxMemory=409;totalMaxMemory=2147483647;totalNumBuckets=113;partitionResolver=null;colocatedWith=null;recoveryDelay=-1;startupRecoveryDelay=0;FixedPartitionAttributes=null;partitionListeners=null];
on VM<ec><v49>:1025]key 1 callbackarg null
> 	at com.gemstone.gemfire.cache.lucene.internal.PartitionedRepositoryManager.getRepository(
> 	at com.gemstone.gemfire.cache.lucene.internal.LuceneEventListener.processEvents(
> 	at com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(
> 	at com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(
> 	at com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(
> 	at
> -----------------------------------------------------------------------
> {noformat}
> It looks like this test is doing a rebalance, so it may be expected that buckets are
not found when writing to the lucent index. The system should probably not log an error just
because a bucket has moved.

This message was sent by Atlassian JIRA

View raw message