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

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

GitHub user karensmolermiller opened a pull request:

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

    GEODE-3014 Document server/region/Lucene index start-up sequence

    @joeymcallister @dihardman @boglesby Please review.

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

    $ git pull https://github.com/karensmolermiller/geode feature/GEODE-3014

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

    https://github.com/apache/geode/pull/554.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 #554
    
----
commit 8d1a1e68ac8b062a2cb78aa6ce232e0c0e43adce
Author: Karen Miller <kmil...@pivotal.io>
Date:   2017-05-31T23:21:27Z

    GEODE-3014 Document server/region/Lucene index start-up sequence

----


> Document gfsh create lucene index and region failure sequence
> -------------------------------------------------------------
>
>                 Key: GEODE-3014
>                 URL: https://issues.apache.org/jira/browse/GEODE-3014
>             Project: Geode
>          Issue Type: Bug
>          Components: docs
>            Reporter: Barry Oglesby
>            Assignee: Karen Smoler Miller
>
> When creating a lucene index and region using gfsh, there is a specific 
> command sequence that causes the region to not be created successfully.
> The sequence that fails is:
> - start server(s)
> - create lucene index
> - start additional server(s)
> - create region
> What fails about this sequence is the lucene index is not saved in cluster 
> configuration until after the region is created. Before the region is 
> created, its only saved locally in existing servers. Since new servers don't 
> have the index when the region is created, the index definitions aren't 
> consistent across servers. This causes the region to be created only in some 
> servers (either all the original ones with the index or all the new ones 
> without the index).
> An alternate sequence that succeeds is:
> - start server(s)
> - create lucene index
> - create region
> - start additional server(s)
> Once the region has been created, then both the lucene index and region are 
> saved in cluster configuration, so new servers will create both the region 
> and index.



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

Reply via email to