Elasticsearch ILM未滚动
Elasticsearch ILM未滚动
提问于 2020-11-06 10:11:20
我已将我的ILM配置为在索引大小为20 30时或在热节点中经过30天后进行转存
但是我的索引通过了20 to，仍然没有传递到冷节点
当我运行：GET _cat/indices?v时，我得到：
green open packetbeat-7.9.2-2020.10.22-000001 RRAnRZrrRZiihscJ3bymig 10 1 63833049 0 44.1gb 22gb你能告诉我怎么解决这个问题吗？
我知道在我的packetbeat文件配置中，我刚刚更改了分片的数量：
setup.template.settings:
index.number_of_shards: 10
index.number_of_replicas: 1当我运行命令GET packetbeat-7.9.2-2020.10.22-000001/_settings时，我得到以下输出：
{
"packetbeat-7.9.2-2020.10.22-000001" : {
"settings" : {
"index" : {
"lifecycle" : {
"name" : "packetbeat",
"rollover_alias" : "packetbeat-7.9.2"
},
"routing" : {
"allocation" : {
"include" : {
"_tier_preference" : "data_content"
}
}
},
"mapping" : {
"total_fields" : {
"limit" : "10000"
}
},
"refresh_interval" : "5s",
"number_of_shards" : "10",
"provided_name" : "<packetbeat-7.9.2-{now/d}-000001>",
"max_docvalue_fields_search" : "200",
"query" : {
"default_field" : [
"message",
"tags",
"agent.ephemeral_id",
"agent.id",
"agent.name",
"agent.type",
"agent.version",
"as.organization.name",
"client.address",
"client.as.organization.name",命令GET /packetbeat-7.9.2-2020.10.22-000001/_ilm/explain的输出为：
{
"indices" : {
"packetbeat-7.9.2-2020.10.22-000001" : {
"index" : "packetbeat-7.9.2-2020.10.22-000001",
"managed" : true,
"policy" : "packetbeat",
"lifecycle_date_millis" : 1603359683835,
"age" : "15.04d",
"phase" : "hot",
"phase_time_millis" : 1603359684332,
"action" : "rollover",
"action_time_millis" : 1603360173138,
"step" : "check-rollover-ready",
"step_time_millis" : 1603360173138,
"phase_execution" : {
"policy" : "packetbeat",
"phase_definition" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_size" : "50gb",
"max_age" : "30d"
}
}
},
"version" : 1,
"modified_date_in_millis" : 1603359683339
}
}
}
}奇怪的是，它是50 it的！
谢谢你的帮忙
回答 1
Stack Overflow用户
回答已采纳
发布于 2020-11-30 15:40:34
所以我找到了这个问题的解决方案。更新策略后，我使用它从索引中删除了该策略，然后将其再次添加到这些索引中。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/64712606
复制相关文章
相似问题
腾讯云开发者
