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 resume from status #49255

Conversation

henningandersen
Copy link
Contributor

Reindex now uses last known good status on failure to ensure that counts
continue from where it left when a node fails.

Also added persistentTaskId to StartReindexResponse and removed a
couple of obsolete todos.

Relates #42612

Reindex now uses last known good status on failure to ensure that counts
continue from where it left when a node fails.

Also added `persistentTaskId` to `StartReindexResponse` and removed a
couple of obsolete todos.

Relates elastic#42612
@henningandersen henningandersen added >non-issue :Distributed Indexing/Reindex Issues relating to reindex that are not caused by issues further down labels Nov 18, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Reindex)

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.

Mostly looks good, just some questions about naming that we can discuss tomorrow if necessary.

@@ -244,6 +248,25 @@ public void rethrottle(float newRequestsPerSecond) {
}
}

public void resetStatus(BulkByScrollTask.Status checkpointStatus) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe initStatus? or setInitialStatus?

out.writeOptionalWriteable(reindexResponse);
}

public String getTaskId() {
return taskId;
}

public String getPersistentTaskId() {
Copy link
Contributor

Choose a reason for hiding this comment

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

I was just working on this on a different branch and I feel like the persistent task id should be the default naming? As in the methods are getTaskId or getReindexTaskId? And the other one be getEphemeralTaskId? Or getCoordinatorNodeTaskId? Or getInitialEphemeralTaskId?

@henningandersen
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/packaging-sample-matrix-unix

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

@henningandersen henningandersen merged commit 12b1728 into elastic:reindex_v2 Mar 3, 2020
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.

3 participants