Skip to content
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.

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

Reindex Throttle Checkpointing #46763

Conversation

henningandersen
Copy link
Contributor

Rather than write checkpoints every time, we now only write at certain intervals.
Revamped the single-writer and finish handling around this to avoid any
waiting/blocking.

Relates #42612

Rather than write every time, we now only write at certain intervals.
Revamped the single-writer and finish handling around this to avoid any
waiting.

Relates elastic#42612
@henningandersen henningandersen added >enhancement v8.0.0 :Distributed Indexing/Reindex Issues relating to reindex that are not caused by issues further down labels Sep 16, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@henningandersen
Copy link
Contributor Author

ci/2 failure reported here: #46907 so
@elasticmachine run elasticsearch-ci/2

Copy link
Contributor

@Tim-Brooks Tim-Brooks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I think we should also consider at some point just having a repeated scheduled checkpoint update at a certain interval. But this seems reasonable.

henningandersen added a commit to henningandersen/elasticsearch that referenced this pull request Sep 23, 2019
Only send back task-id to client after all subtasks have started to
stay compatible with tests requiring this.

Relates elastic#46763 (test failure) and elastic#42612
this.value = newValue;
if (scheduledWrite == null) {
// schedule is non-blocking
scheduledWrite = threadPool.schedule(this::onScheduleTimeout, getDelay(now), ThreadPool.Names.SAME);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

schedule loses the thread context. Given that we are afterwards writing to an index (possibly running with security enabled), I wonder if that thread context is relevant.

@henningandersen
Copy link
Contributor Author

ci/1 failure to run reindex/80_slices/Multiple slices with rethrottle has been fixed here in #46967, intend to merge to FB with that failure.

henningandersen added a commit that referenced this pull request Sep 24, 2019
Only send back task-id to client after all subtasks have started to
stay compatible with tests requiring this.

Relates #46763 (test failure) and #42612
@henningandersen henningandersen merged commit 4230ecb into elastic:reindex_v2 Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/Reindex Issues relating to reindex that are not caused by issues further down >non-issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants