Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add serverless ttl job interval desc #18420

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions tidb-cloud/serverless-limitations.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,10 @@ We are constantly filling in the feature gaps between TiDB Serverless and TiDB D
- [Changefeed](/tidb-cloud/changefeed-overview.md) is not supported for TiDB Serverless currently.
- [Data Migration](/tidb-cloud/migrate-from-mysql-using-data-migration.md) is not supported for TiDB Serverless currently.

### Time to live (TTL)

- In TiDB Serverless, the [`TTL_JOB_INTERVAL`](/time-to-live.md#ttl-job) attribute for a table is fixed at `15m` and cannot be modified. This means that TiDB Serverless schedules a background job every 15 minutes to clean up expired data.

### Others

- Transaction can not last longer than 30 minutes.
Expand Down
8 changes: 8 additions & 0 deletions time-to-live.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,14 @@ CREATE TABLE orders (

## TTL job

<CustomContent platform="tidb-cloud">

> **Note:**
>
> In TiDB Serverless, the `TTL_JOB_INTERVAL` attribute for a table is fixed at `15m` and cannot be modified. This means that TiDB Serverless schedules a background job every 15 minutes to clean up expired data.

</CustomContent>

For each table with a TTL attribute, TiDB internally schedules a background job to clean up expired data. You can customize the execution period of these jobs by setting the `TTL_JOB_INTERVAL` attribute for the table. The following example sets the background cleanup jobs for the table `orders` to run once every 24 hours:

```sql
Expand Down
Loading