---
title: Change settings in ilm.json
description: 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 onilm.json configuration, see Automatic rollover index.
component: pingintelligence
version: 5.1
page_id: pingintelligence:pingintelligence_production_deployment:pingintelligence_changing_settings_ilm_json
canonical_url: https://docs.pingidentity.com/pingintelligence/5.1/pingintelligence_production_deployment/pingintelligence_changing_settings_ilm_json.html
revdate: March 21, 2024
---

# Change settings in ilm.json

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](../pingintelligence_dashboard/pingintelligence_automatic_rollover_index.html).

| Variable   | Description                                                                                                                                                                                                                                                                                                                                                                        |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `max_size` | Defines the maximum size of the Elasticsearch rollover index. When the index size reaches the defined value, it rolls over.`max_size` value should be a positive non-zero number. Allowed units are MB and GB.                                                                                                                                                                     |
| `max_age`  | Defines the maximum age of the Elasticsearch rollover index configuration. `max_age` value should be a positive non-zero number. Allowed units are` h` for hours and `d` for the number of days. If both `max_size` and` max_age` are configured, then the index rolls over based on the value that is achieved first.                                                             |
| `min_age`  | Defines the minimum age, after which the Elasticsearch rollover index enters into a different phase. Allowed units are` h` for hours and `d` for the number of days. Every index starts from `hot` phase. For more information on the phases in an index life cycle, see [Automatic rollover index](../pingintelligence_dashboard/pingintelligence_automatic_rollover_index.html). |
| `priority` | 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`dashboard-default.yml` file. For more information, see [Change settings in dashboard-defaults.yml](pingintelligence_changing_settings_dashboard_defaults_yml.html). |

The following is a sample `ilm.json` file.

```json
{
  "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
          }
        }
      }
    }
  }
}
```