geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-3014) Document gfsh create lucene index and region failure sequence
Date Thu, 01 Jun 2017 16:41:04 GMT


ASF subversion and git services commented on GEODE-3014:

Commit 8c81965bec2c75f66b829e674ee7269d1ed2a8a6 in geode's branch refs/heads/develop from
[;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:
>             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
> 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

View raw message