Hello,
We recently upgraded our elasticsearch stack to 7.11.2 from 7.6.0 and are seeing an issue when attempting PUTS on indexes that don't exist:
"message": "failed to handle exception response [org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler/org.elasticsearch.transport.TransportService$6/[indices:admin/auto_create]:org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$1@5cbcbb03/org.elasticsearch.action.support.TransportAction$1@63c6e8ba]", "cluster.uuid": "WZjUh9hSRyK6IkZwNMF8rQ", "node.id": "jn7PgJoRRdCE3WbC4x2J8A"
"stacktrace": ["java.lang.ClassCastException: class org.elasticsearch.transport.RemoteTransportException cannot be cast to class org.elasticsearch.index.IndexNotFoundException (org.elasticsearch.transport.RemoteTransportException and org.elasticsearch.index.IndexNotFoundException are in unnamed module of loader 'app')",
"at org.elasticsearch.action.bulk.TransportBulkAction$1.onFailure(TransportBulkAction.java:263) ~[elasticsearch-7.11.2.jar:7.11.2]",
at "at org.elasticsearch.action.support.TransportAction$1.onFailure(TransportAction.java:92) ~[elasticsearch-7.11.2.jar:7.11.2]",
"at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$1.handleException(TransportMasterNodeAction.java:177) ~[elasticsearch-7.11.2.jar:7.11.2]",
Add a template parameter to override auto_create_index value by pugnascotia · Pull Request #61858 · elastic/elasticsearch · GitHub Potentially related to this PR? We currently use an elastic search yml to define auto create index rules that are disallowing these extraneous indexes to be created
elasticsearch.yml: |
action.auto_create_index: ".watches,.triggered_watches,.watcher-history*,.kibana*,.monitoring*"
Before we updated we would simply get a 404 response back indicating that the index isn't found and to simply move on, but with these class cast exceptions we're not getting that behavior.