ROLLUP_NO_MATCHING_INDICES
elasticsearch
config_error
ai_generated
true
ElasticsearchException: Rollup job [my_rollup] cannot be started because the index pattern [logs-*] does not match any existing indices
ID: elasticsearch/rollup-job-not-matching-indices
82%Fix Rate
83%Confidence
1Evidence
2024-04-05First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| Elasticsearch 7.13 | active | — | — | — |
| Elasticsearch 8.3 | active | — | — | — |
| Elasticsearch 8.12 | active | — | — | — |
Root Cause
The rollup job's index pattern does not match any indices in the cluster, preventing job initialization.
generic中文
汇总作业的索引模式不匹配集群中的任何索引,阻止作业初始化。
Official Documentation
https://www.elastic.co/guide/en/elasticsearch/reference/current/rollup-getting-started.htmlWorkarounds
-
90% success Verify existing indices with `GET _cat/indices/logs-*` and adjust the rollup job pattern to match: `PUT _rollup/job/my_rollup/_stop` then `PUT _rollup/job/my_rollup {"index_pattern": "logs-2025-*"}`
Verify existing indices with `GET _cat/indices/logs-*` and adjust the rollup job pattern to match: `PUT _rollup/job/my_rollup/_stop` then `PUT _rollup/job/my_rollup {"index_pattern": "logs-2025-*"}` -
85% success Create sample data indices matching the pattern before starting the job: `POST logs-2025-01/_doc {"timestamp": "2025-01-01", "value": 10}`
Create sample data indices matching the pattern before starting the job: `POST logs-2025-01/_doc {"timestamp": "2025-01-01", "value": 10}`
中文步骤
使用`GET _cat/indices/logs-*`验证现有索引,并调整汇总作业模式以匹配:`PUT _rollup/job/my_rollup/_stop`然后`PUT _rollup/job/my_rollup {"index_pattern": "logs-2025-*"}`在启动作业前创建匹配模式的示例数据索引:`POST logs-2025-01/_doc {"timestamp": "2025-01-01", "value": 10}`
Dead Ends
Common approaches that don't work:
-
Creating an empty index matching the pattern (e.g., `PUT logs-2025`) without data
60% fail
The rollup job may start but will produce no results, and the empty index may cause other issues.
-
Modifying the rollup job to use a wildcard pattern like `*`
70% fail
This may match unintended indices, causing performance degradation or incorrect rollups.
-
Restarting the rollup job without checking index existence
90% fail
The same error will recur as the index pattern remains unmatched.