Briefly, this error occurs when an Elasticsearch reset operation has been successfully executed. This is not an error message, but a confirmation message indicating that the reset operation has been completed successfully. If you didn’t intend to reset, you may have lost data. To resolve this, ensure to backup your data regularly and only perform reset operations when necessary. If the reset was intentional and you’re still facing issues, check your Elasticsearch configuration or consult your logs for more detailed information.
This guide will help you check for common problems that cause the log ” [{}] Reset has successfully completed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[{}] Reset has successfully completed” classname is TransportResetJobAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
);
}
private void finishSuccessfulReset(String jobId; ActionListener listener) {
jobConfigProvider.updateJobAfterReset(jobId; ActionListener.wrap(blockReasonUpdatedResponse -> {
logger.info("[{}] Reset has successfully completed"; jobId);
auditor.info(jobId; Messages.getMessage(Messages.JOB_AUDIT_RESET));
listener.onResponse(AcknowledgedResponse.of(true));
}; listener::onFailure));
}
[ratemypost]
