You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Shelley Lynn Hughes-Godfrey (JIRA)" <ji...@apache.org> on 2018/03/07 17:02:00 UTC

[jira] [Resolved] (GEODE-4764) NPEs encountered during lucene create index (on existing region)

     [ https://issues.apache.org/jira/browse/GEODE-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shelley Lynn Hughes-Godfrey resolved GEODE-4764.
------------------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

Fixed on develop:

{noformat}
commit 70415070443137941ff1c1b750af81cf4442f6ef
Author: Lynn Hughes-Godfrey <lh...@pivotal.io>
Date:   Thu Mar 1 17:22:23 2018 -0800

    GEODE-4764: Address NPEs during Lucene index creation on existing region
    
    * Don't add the aeq to the region until the data region has been created
    * When iterating over list of local primary bucketIds (during reindexing), check for null return value when retrieving a specific bucket
    * Added tests for same.
{noformat}

> NPEs encountered during lucene create index (on existing region)
> ----------------------------------------------------------------
>
>                 Key: GEODE-4764
>                 URL: https://issues.apache.org/jira/browse/GEODE-4764
>             Project: Geode
>          Issue Type: Sub-task
>          Components: lucene
>    Affects Versions: 1.5.0
>            Reporter: Shelley Lynn Hughes-Godfrey
>            Assignee: Shelley Lynn Hughes-Godfrey
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There are currently two potential NPEs in LuceneServiceImpl during index creation on an existing region.
> The first occurs when a bucket is moved during indexing:
> {noformat}
>         at org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createLuceneIndexOnDataRegion(LuceneServiceImpl.java:294)
>         at org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndexOnExistingRegion(LuceneServiceImpl.java:277)
>         at org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:257)
>         at org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:226)
>         at org.apache.geode.cache.lucene.internal.LuceneIndexFactoryImpl.create(LuceneIndexFactoryImpl.java:70)
> {noformat}
> The second occurs when the LuceneEventListener attempts to process events before the Lucene Index has been fully initialized (and userRegion set).
> {noformat}
>         at org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:164)
>         at org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:80)
>         at org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:610)
>         at org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1051)
> Caused by: java.lang.NullPointerException
>         at org.apache.geode.cache.lucene.internal.AbstractPartitionedRepositoryManager.getRepository(AbstractPartitionedRepositoryManager.java:70)
>         at org.apache.geode.cache.lucene.internal.LuceneEventListener.process(LuceneEventListener.java:86)
>         at org.apache.geode.cache.lucene.internal.LuceneEventListener.processEvents(LuceneEventListener.java:63)
>         at org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:154)
>         ... 3 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)