Skip to content

Recommend force-merging after stopping indexing but before marking the index read-only #41687

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
DaveCTurner opened this issue Apr 30, 2019 · 1 comment · Fixed by #44684
Closed

Recommend force-merging after stopping indexing but before marking the index read-only #41687

DaveCTurner opened this issue Apr 30, 2019 · 1 comment · Fixed by #44684
Labels
:Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. >docs General docs changes help wanted adoptme

Comments

@DaveCTurner
Copy link
Contributor

In #28869 we added a note saying that you should only really force-merge a read-only index. This is a bit misleading: you can't force merge an index that is actually read-only, we really mean to do this on indices that are not going to be written to any more (see comments on #28843). We should clarify these docs to distinguish no-more-indexing from has-a-read-only-block.

Replaces #41624.
@DaveCTurner DaveCTurner added >docs General docs changes help wanted adoptme :Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. labels Apr 30, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@DaveCTurner DaveCTurner mentioned this issue Apr 30, 2019
Closed
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this issue Jul 22, 2019
@DaveCTurner
Expand docs on force-merge and global ordinals
718db1a 
Some small clarifications about force-merging and global ordinals, particularly
that global ordinals are cheap on a single-segment index and how this relates
to frozen indices.

Fixes elastic#41687
@DaveCTurner DaveCTurner mentioned this issue Jul 22, 2019
Merged
DaveCTurner added a commit that referenced this issue Jul 23, 2019
@DaveCTurner
Expand docs on force-merge and global ordinals (#44684)
534d2e5 
Some small clarifications about force-merging and global ordinals, particularly
that global ordinals are cheap on a single-segment index and how this relates
to frozen indices.

Fixes #41687
DaveCTurner added a commit that referenced this issue Jul 23, 2019
@DaveCTurner
Expand docs on force-merge and global ordinals (#44684)
8516fb0 
Some small clarifications about force-merging and global ordinals, particularly
that global ordinals are cheap on a single-segment index and how this relates
to frozen indices.

Fixes #41687
@stsourlidakis stsourlidakis mentioned this issue Mar 20, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. >docs General docs changes help wanted adoptme
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Expand docs on force-merge and global ordinals DaveCTurner/elasticsearch
2 participants
@DaveCTurner @elasticmachine