# Using the same index for a year

**URL:** <https://discuss.elastic.co/t/using-the-same-index-for-a-year/307132>\
**Category:** Elasticsearch\
**Created:** [June 14, 2022, 10:31am UTC](https://discuss.elastic.co/t/using-the-same-index-for-a-year/307132 "2022-06-14T10:31:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mertkaant](https://avatars.discourse-cdn.com/v4/letter/m/9fc29f/32.png) [@mertkaant](https://discuss.elastic.co/u/mertkaant)\
**Post date:** [June 14, 2022, 10:31am UTC](https://discuss.elastic.co/t/using-the-same-index-for-a-year/307132/1 "2022-06-14T10:31:59Z")

</div>

Hello, elastic community,

I have a new index and I'm writing small data daily to this index. I want to achieve lifecycle management for this index and about that, I thought since this is a really small index can I configure lifecycle management like this?

- Keep the index in hot phase for a year then rollover to a new index and move the old index to the cold phase.

If it was a big index I would go with recommended defaults which are "rollover if the index is 30 days old or any primary shard's size \> 50GB"

Notes:

- Even if I use the same index for writing/reading for a year, the index size won't pass 100GB.
- This index will be in production and it is a highly used environment

My questions are:

1. Can I use the same index for a year with keeping that index in the hot phase? Is it okay for cluster/index health?
2. Is this gonna trouble me in the future? about performance issues?
3. Since there won't be any date implementation on the index name, am I going to search fastly on this index?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 14, 2022, 11:20pm UTC](https://discuss.elastic.co/t/using-the-same-index-for-a-year/307132/2 "2022-06-14T23:20:34Z")

</div>

Depends what you mean by small, but yes this is a totally reasonable approach for low volume data.

---

<div class="post-metadata">

**Author:** ![mertkaant](https://avatars.discourse-cdn.com/v4/letter/m/9fc29f/32.png) [@mertkaant](https://discuss.elastic.co/u/mertkaant)\
**Post date:** [June 15, 2022, 7:31am UTC](https://discuss.elastic.co/t/using-the-same-index-for-a-year/307132/3 "2022-06-15T07:31:13Z")

</div>

The data will be around 50KB-10MB for a day. I'll set up a lifecycle policy with 1-year hot phase scenario. Thanks for the reply!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 13, 2022, 7:32am UTC](https://discuss.elastic.co/t/using-the-same-index-for-a-year/307132/4 "2022-07-13T07:32:08Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.