Failed to execute input for watch ; reason – How to solve related issues

Failed to execute input for watch ; reason – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

This log is related to search problems, in addition to reading the guide below you can use the free Search Log Analyzer. With Opster’s Analyzer, you can easily locate slow searches and understand what led to them adding additional load to your system. You’ll receive customized recommendations for how to reduce search latency and improve your search performance. The tool is free and takes just 2 minutes to run.

Log Context

Log “Failed to execute [{}] input for watch [{}]; reason [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             Script template = input.getRequest().getOrCreateTemplate();
            String renderedTemplate = searchTemplateService.renderTemplate(template; ctx; payload);
            request = new WatcherSearchTemplateRequest(input.getRequest(); new BytesArray(renderedTemplate));
            return doExecute(ctx; request);
        } catch (Exception e) {
            logger.error("failed to execute [{}] input for watch [{}]; reason [{}]"; TYPE;; e.getMessage());
            return new SearchInput.Result(request; e);

    SearchInput.Result doExecute(WatchExecutionContext ctx; WatcherSearchTemplateRequest request) throws Exception {


Run the Check-Up to get customized recommendations like this:


The high disk watermark threshold is about to be reached in specific nodes



There are various “watermark” thresholds on each Elasticsearch cluster. When the high disk watermark threshold has been exceeded, it means disk space is running out. The node will…



Based on your specific ES deployment you should…


X-PUT curl -H [a customized code snippet to resolve the issue]

Optimize Elasticsearch Performance

Run The Tool