[ESRCH-45] Index consistency on JVM crash Created: 01/Dec/20 Updated: 02/Dec/20 Resolved: 02/Dec/20 |
|
| Status: | Closed |
| Project: | External Enterprise Search |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Michael Duerig | Assignee: | Michael Duerig |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | Elastic Search |
| Description |
GoalClarify expectations, goals and options wrt. keeping the ES index consistent. ProblemThe SearchIndex interface does not give us consistency guarantees beyond those that we have for the integrated Lucene index in Jackrabbit. After a server / JVM crash the index can still go out of sync, requiring a full re-index. Solution sketchTo improve on index resilience we would need to:
Implementation considerations
|