Skip to main content


...About 1 min


IoTDB supports storage-level TTL settings, which means it is able to delete old data automatically and periodically. The benefit of using TTL is that hopefully you can control the total disk space usage and prevent the machine from running out of disks. Moreover, the query performance may downgrade as the total number of files goes up and the memory usage also increase as there are more files. Timely removing such files helps to keep at a high query performance level and reduce memory usage.


The SQL Statement for setting TTL is as follow:

IoTDB> set ttl to root.ln 3600000

This example means that for data in root.ln, only that of the latest 1 hour will remain, the older one is removed or made invisible.

Unset TTL

To unset TTL, we can use follwing SQL statement:

IoTDB> unset ttl to root.ln

After unset TTL, all data will be accepted in root.ln

Show TTL

To Show TTL, we can use following SQL statement:

IoTDB> SHOW TTL ON StorageGroupNames

The SHOW ALL TTL example gives the TTL for all storage groups.
The SHOW TTL ON root.group1 , root.group2 , root.group3 example shows the TTL for the three storage
groups specified.
Note: the TTL for storage groups that do not have a TTL set will display as null.

Copyright © 2024 The Apache Software Foundation.
Apache IoTDB, IoTDB, Apache, the Apache feather logo, and the Apache IoTDB project logo are either registered trademarks or trademarks of The Apache Software Foundation in all countries

Have a question? Connect with us on QQ, WeChat, or Slack. Join the community now.