# TSDS - manual rollover

**URL:** <https://discuss.elastic.co/t/tsds-manual-rollover/323227>\
**Category:** Elasticsearch\
**Tags:** datastreams\
**Created:** [January 16, 2023, 8:17am UTC](https://discuss.elastic.co/t/tsds-manual-rollover/323227 "2023-01-16T08:17:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sako](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@Sako](https://discuss.elastic.co/u/Sako)\
**Post date:** [January 16, 2023, 8:17am UTC](https://discuss.elastic.co/t/tsds-manual-rollover/323227/1 "2023-01-16T08:17:18Z")

</div>

Hi,

I try to use Timeseries Data Streams (TSDS) for telemetry data from network devices to use the new downsampling features later on. I also use ILM to automate the rollover and lifecycle for the TSDS.

Under certain circumstance I need to trigger a rollover manually, like for new mappings for the DS.  
If I trigger a rollover via the API, the old backing index still gets the documents as the index.time\_series.end\_time is still in the future. I then cannot change this setting to the current time to force the documents to the new backing index.

Is there a way to manually rollover a TSDS or what steps are needed to do this?

Greetings

---

<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:** [February 13, 2023, 8:18am UTC](https://discuss.elastic.co/t/tsds-manual-rollover/323227/2 "2023-02-13T08:18:04Z")

</div>

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