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

ASF GitHub Bot commented on GEODE-2768:
---------------------------------------

GitHub user jhuynh1 opened a pull request:

    https://github.com/apache/geode/pull/451

    GEODE-2768: Lucene Queries executed before index is fully created sho…

    …uld be retried
    
      * Added a sleep to prevent rapid retries which lead to stack overflow
      * Sleep can be removed when Function Execution retry does not add to stack

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/geode feature/GEODE-2768

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode/pull/451.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #451
    
----
commit 60f5f06f18f8ea6c1d176a43a25bfbb4086e2f21
Author: Jason Huynh <huyn...@gmail.com>
Date:   2017-04-12T18:39:28Z

    GEODE-2768: Lucene Queries executed before index is fully created should be 
retried
    
      * Added a sleep to prevent rapid retries which lead to stack overflow
      * Sleep can be removed when Function Execution retry does not add to stack

----


> Lucene Queries executed before index is fully created should be retried
> -----------------------------------------------------------------------
>
>                 Key: GEODE-2768
>                 URL: https://issues.apache.org/jira/browse/GEODE-2768
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Jason Huynh
>            Assignee: Jason Huynh
>
> With the feature to destroy a Lucene Index, parts of the querying function 
> were changed to handle the event where we execute a query on an index that is 
> no longer present.  However, the scenario where we execute a query on an 
> index that is defined but has not been created can also arise. 
> We want to handle the case where we have defined the index, but have yet to 
> create it due to a brief window in restart.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to