Briefly, this error occurs when Elasticsearch tries to access a calendar with a specific ID, but it can’t find it. This could be due to the calendar being deleted, not yet created, or the ID being incorrect. To resolve this issue, you can verify if the calendar ID is correct, check if the calendar exists, or create a new calendar with the specified ID if it doesn’t exist.
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 + “]” class name is TransportDeleteCalendarAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
ActionListenercalendarListener = ActionListener.wrap(calendar -> { // 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 + "]")); return; } jobManager.updateProcessOnCalendarChanged( calendar.getJobIds();
