You can change the default settings of Index Lifecycle Management (ILM) policy by editing the /<pi-install-path>/pingidentity/pi-api-deployment/config/ilm.json file.
The ILM policy allows you to manage the lifecycle of the Elasticsearch indices. The following table lists the variables that you can set in the ilm.json file. For more information on ilm.json configuration, see Automatic rollover index.
Variable |
Description |
---|---|
|
Defines the maximum size of the Elasticsearch rollover index. When the index size
reaches the defined value, it rolls over. |
|
Defines the maximum age of the Elasticsearch rollover index configuration. The
|
|
Defines the minimum age, after which the Elasticsearch rollover index enters into a
different phase. Allowed units are |
|
Defines the sequence in which indices are reloaded back into memory when Elasticsearch restarts. Use a positive integer number to set the priority. |
Rollover index configuration takes effect only when enable_xpack
is set to
true
in the dashboard-default.yml file. For more
information, see Changing settings in dashboard-defaults.yml.
The following is a sample ilm.json file.
{
"policy": {
"phases": {
"hot": {
"actions": {
"rollover": {
"max_size": "7GB",
"max_age": "7d"
},
"set_priority": {
"priority": 100
}
}
},
"warm": {
"min_age": "30d",
"actions": {
"set_priority": {
"priority": 50
}
}
},
"cold": {
"min_age": "90d",
"actions": {
"freeze": {},
"set_priority": {
"priority": 0
}
}
}
}
}
}