No calendar with id ” + calendarId + ” – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” No calendar with id ” + calendarId + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “No calendar with id [” + calendarId + “]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// Delete calendar and events
 DeleteByQueryRequest dbqRequest = buildDeleteByQuery(calendarId);
 executeAsyncWithOrigin(client; ML_ORIGIN; DeleteByQueryAction.INSTANCE; dbqRequest; ActionListener.wrap(
 response -> {
 if (response.getDeleted() == 0) {
 listener.onFailure(new ResourceNotFoundException("No calendar with id [" + calendarId + "]"));
 jobManager.updateProcessOnCalendarChanged(calendar.getJobIds(); ActionListener.wrap(
 r -> listener.onResponse(new AcknowledgedResponse(true));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content