[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-3014:


Commit 335c109d5c7d1ed427b345636c0af8b6c1636f3b in geode's branch 
refs/heads/release/1.2.0 from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=335c109 ]

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

This closes #554


> 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)

[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-3014:


Commit 8c81965bec2c75f66b829e674ee7269d1ed2a8a6 in geode's branch 
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=8c81965 ]

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

This closes #554


> 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)

[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> 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)

[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence

[ASF GitHub Bot (JIRA)]

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

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

Github user dihardman commented on the issue:

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

On Wed, May 31, 2017 at 4:24 PM, Karen Miller 
wrote:

> @joeymcallister  @dihardman
>  @boglesby 
> Please review.
> --
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/apache/geode/pull/554
> Commit Summary
>
>- GEODE-3014 Document server/region/Lucene index start-up sequence
>
> File Changes
>
>- *M* geode-docs/tools_modules/lucene_integration.html.md.erb
> (12)
>
> Patch Links:
>
>- https://github.com/apache/geode/pull/554.patch
>- https://github.com/apache/geode/pull/554.diff
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or mute the thread
> 

> .
>



> 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)

[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence

[ASF GitHub Bot (JIRA)]

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

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

Github user joeymcallister commented on the issue:

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


> 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)

[jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 
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)