# Opensearch life cycle management for docs over 30 days

**URL:** <https://forum.opensearch.org/t/opensearch-life-cycle-management-for-docs-over-30-days/23780>\
**Category:** OpenSearch\
**Created:** [March 14, 2025, 10:28pm UTC](https://forum.opensearch.org/t/opensearch-life-cycle-management-for-docs-over-30-days/23780 "2025-03-14T22:28:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rajesh2024](https://avatars.discourse-cdn.com/v4/letter/r/7cd45c/32.png) [@Rajesh2024](https://forum.opensearch.org/u/Rajesh2024)\
**Post date:** [March 14, 2025, 10:28pm UTC](https://forum.opensearch.org/t/opensearch-life-cycle-management-for-docs-over-30-days/23780/1 "2025-03-14T22:28:07Z")

</div>

**2.16** (relevant - OpenSearch/Dashboard/Server OS/Browser):

**Describe the issue** :  
I want to maintain the lifecycle management of an elastic search or opensearch doc over x days. \_delete\_by\_query api help with the job, however i understand this also comes with some performance impact on query/read on delete of large data set, add segment merging to it. What is the best way to accomplish this. Would rollover be a better option here ? Incase i have to maintain the state of the doc for 90days or over, would reading from multiple indexes, over large data and aggregation have not impact.

\_delete\_query\_api Index State Management

**Configuration** :

**Relevant Logs or Screenshots** :