Major Description
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.
Attachments
Issue Links
- links to
