We have an exiting datastream foo-stream
and two backing indices .foo-stream-000001
and .foo-stream-000002
.
Our application is writing/reading to the index foo-stream
and the overall expectation is that ILM would automatically create and adjust the writable index (-00000#) as the policy thresholds are met.
The policy:
"rollover": {
"max_age": "1d",
"max_size": "50gb"
}
The problem is that the index .foo-stream-000001
is 32 days old and contains 1.1TB of data. We found that the ILM policy was not attached to this specific index, but does match the index pattern. When manually applying the ILM policy to this index, .foo-stream-000002
was created, but it contains no documents and the .foo-stream-000001
has stopped receiving documents.
I would have expected that when applying the ILM Policy to .foo-stream-000001
it would have split the data into at least 32 different indexes. What am I missing?
The explain for .foo-stream-000001
{
"indices": {
".foo-stream-000001": {
"index": ".foo-stream-000001",
"managed": true,
"phase_execution": {
"policy": "foo-stream",
"modified_date_in_millis": 1615925871750,
"phase_definition": {
"actions": {
"rollover": {
"max_age": "1d",
"max_size": "50gb"
},
"set_priority": {
"priority": 100
}
},
"min_age": "0ms"
},
"version": 5
},
"action_time_millis": 1615919902092,
"age": "2.22h",
"step_time_millis": 1615919902092,
"phase_time_millis": 1615918967960,
"phase": "hot",
"step": "complete",
"lifecycle_date_millis": 1615919894909,
"policy": "foo-stream",
"action": "complete"
}
}
}