This Security Exception occurred when checking to see if the index already exists but fails silently - nothing logged. The Elasticsearch Connector ignores the Security Exception and continues assuming the index didn't exists when it really did. Therefore when the Elasticsearch Connector Task tried to ...
co.elastic.clients.elasticsearch._types.ElasticsearchException: [es/indices.create] failed: [resource_already_exists_exception] index [operate-sequence-flow-8.3.0_/mi8AWfmuQWqAM1k79lkdPg] already exists at co.elastic.clients.transport.ElasticsearchTransportBase.getApiResponse ( co/elastic.clients.transp...
Caused by: org.uberfire.java.nio.IOException: java.nio.file.FileAlreadyExistsException: .index/system/datasets/write.lock Caused by: java.nio.file.FileAlreadyExistsException: .index/system/datasets/write.lock\"}}" The kie-server deployment is successful. But the decision-central deployment failed ...