[
https://issues.apache.org/jira/browse/GEODE-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336714#comment-15336714
]
ASF GitHub Bot commented on GEODE-1557:
---------------------------------------
Github user nabarunnag commented on the issue:
https://github.com/apache/incubator-geode/pull/168
I was just curious as to know why manager was asked to throw a
BucketNotFoundException but in the verification we are checking that logger was
never called with an error method containing any exception parameter. Why is it
not checking just for BucketNotFoundException but rather all Exceptions.
`verify(log, never()).error(anyString(), any(Exception.class));`
@upthewaterspout
> LuceneQueriesPeerPRDUnitTest.returnCorrectResultsAfterRebalance fails with
> suspect string error
> -----------------------------------------------------------------------------------------------
>
> Key: GEODE-1557
> URL: https://issues.apache.org/jira/browse/GEODE-1557
> 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 192.168.1.17(10580)<ec><v49>:1025]key 1 callbackarg null
> at
> com.gemstone.gemfire.cache.lucene.internal.PartitionedRepositoryManager.getRepository(PartitionedRepositoryManager.java:102)
> at
> com.gemstone.gemfire.cache.lucene.internal.LuceneEventListener.processEvents(LuceneEventListener.java:72)
> at
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:168)
> at
> com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:87)
> at
> com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:613)
> at
> com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1058)
> -----------------------------------------------------------------------
> {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
(v6.3.4#6332)
