由于我的錯誤，我洗掉了活動索引，現在 Elasticsearch 的 cronjob 引發了錯誤：
Current write index for app-write:
Checking results from _rollover call
Calculating next write index based on current write index...
Next write index for app-write: -000001
Checking if -000001 exists
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","resource.type":"index_or_alias","resource.id":"-000001","index":"-000001"}],"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","resource.type":"index_or_alias","resource.id":"-000001","index":"-000001"},"status":404}
您知道如何解決此問題的任何解決方法嗎？
uj5u.com熱心網友回復：
如果您錯誤地洗掉了活動索引并且沒有任何快照或備份，那么您將無法恢復您的資料。
但是，您可以通過使用以下命令重新創建活動索引來使行程再次運行（確保正確替換whatever_name_your_index_had為您不小心洗掉的索引的實際名稱）：
PUT whatever_name_your_index_had-000001
{
"aliases": {
"app-write": {
"is_write_index": true
}
}
}
轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/320943.html