Successfully updated remote job – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Successfully updated remote job ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Successfully updated remote job [{}]” classname is UpdateJobProcessNotifier.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         executeAsyncWithOrigin(client; ML_ORIGIN; UpdateProcessAction.INSTANCE; request;
                new ActionListener() {
                    
Override
                    public void onResponse(Response response) {
                        if (response.isUpdated()) {
                            logger.info("Successfully updated remote job [{}]"; update.getJobId());
                            updateHolder.listener.onResponse(true);
                        } else {
                            String msg = "Failed to update remote job [" + update.getJobId() + "]";
                            logger.error(msg);
                            updateHolder.listener.onFailure(ExceptionsHelper.serverError(msg));



 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content