Operate don't show any processes

Camunda 8 Topics
1

I use self-hosted Camunda 8.5 with docker compose. Everything was working fine, but after six months, an error occurred:
Error on exporting record with key 2251799884010885

io.camunda.zeebe.exporter.ElasticsearchExporterException: Failed to flush bulk request: [Failed to flush 1 item(s) of bulk request [type: validation_exception, reason: Validation Failed: 1: this action would add [1] shards, but this cluster currently has [3500]/[3500] maximum normal shards open;]]

I checked ElasticSearch and found out that all shards are busy. I setted up Index Lifecycle Management (ILM) on Elastic with this config:

{
“policy”: {
“phases”: {
“hot”: {
“actions”: {}
},
“delete”: {
“min_age”: “30d”,
“actions”: {
“delete”: {}
}
}
}
}
}

Old indexes and shards were deleted but Operate stopped show process. I see these errors:

Elasticsearch exception [type=index_not_found_exception, reason=no such index [operate-process-8.3.0_alias]]
Elasticsearch exception [type=index_not_found_exception, reason=no such index [operate-batch-operation-1.0.0_alias]]
Elasticsearch exception [type=index_not_found_exception, reason=no such index [operate-operation-8.4.0_alias]]

How can I restore indexes? And how can I setup ILM or something to clean old indexes but to not delete necessary for work?

2

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.