docs: Spill Data Storage (#1632)

* Spill Data Storage

* updates

Author: soyeric128

docs/en/guides/10-deploy/04-references/02-node-config/02-query-config.md

@@ -256,3 +256,23 @@ The following is a list of the parameters available within the [cache.disk] sect
 | --------- | -------------------------------------------------------------------------------------------------------- |
 | path      | The path where the cache is stored when using disk cache.                                                |
 | max_bytes | The maximum amount of cached data in bytes when using disk cache. Defaults to 21474836480 bytes (20 GB). |
+
+## [spill] Section
+
+The following is a list of the parameters available within the [spill] section:
+
+| Parameter                                  | Description                                                                                                   |
+|--------------------------------------------|---------------------------------------------------------------------------------------------------------------|
+| spill_local_disk_path                      | Specifies the directory path where spilled data will be stored on the local disk.                             |
+| spill_local_disk_reserved_space_percentage | Defines the percentage of disk space that will be reserved and not used for spill. The default value is `30`. |
+| spill_local_disk_max_bytes                 | Sets the maximum number of bytes allowed for spilling data to the local disk. Defaults to unlimited.          |
+
+### [spill.storage] Section
+
+The following is a list of the parameters available within the [spill.storage] section:
+
+| Parameter | Description                                                        |
+|-----------|--------------------------------------------------------------------|
+| type      | Specifies the storage type for remote spilling, for example, `s3`. |
+
+To specify a specific storage, use the parameters in the [storage Section](#storage-section). For examples, see [Configuring Spill Storage](/guides/data-management/data-recycle#configuring-spill-storage). 

docs/en/guides/57-data-management/04-data-recycle.md

@@ -12,6 +12,54 @@ There are two types of data:
 
 If the data size is significant, you can run several commands ([Enterprise Edition Features](/guides/products/dee/enterprise-features)) to delete these data and free up storage space.
 
+## Spill Data Storage
+
+Self-hosted Databend supports spilling intermediate query results to disk when memory usage exceeds available limits. Users can configure where spill data is stored, choosing between local disk storage and a remote S3-compatible bucket.
+
+### Spill Storage Options
+
+Databend provides the following spill storage configurations:
+
+- Local Disk Storage: Spilled data is written to a specified local directory in the query node. Please note that local disk storage is supported only for [Windows Functions](/sql/sql-functions/window-functions/).
+- Remote S3-Compatible Storage: Spilled data is stored in an external bucket.
+- Default Storage: If no spill storage is configured, Databend spills data to the default storage bucket along with your table data.
+
+### Spill Priority
+
+If both local and S3-compatible spill storage are configured, Databend follows this order:
+
+1. Spill to local disk first (if configured).
+2. Spill to remote S3-compatible storage when local disk space is insufficient.
+3. Spill to Databend’s default storage bucket if neither local nor external S3-compatible storage is configured.
+
+### Configuring Spill Storage
+
+To configure spill storage, update the [databend-query.toml](https://github.com/databendlabs/databend/blob/main/scripts/distribution/configs/databend-query.toml) configuration file.
+
+This example sets Databend to use up to 1 TB of local disk space for spill operations, while reserving 40% of the disk for system use:
+
+```toml
+[spill]
+spill_local_disk_path = "/data1/databend/databend_spill"
+spill_local_disk_reserved_space_percentage = 40
+spill_local_disk_max_bytes = 1099511627776
+```
+
+This example sets Databend to use MinIO as an S3-compatible storage service for spill operations:
+
+```toml
+[spill]
+[spill.storage]
+type = "s3"
+[spill.storage.s3]
+bucket = "databend"
+root = "admin"
+endpoint_url = "http://127.0.0.1:9900"
+access_key_id = "minioadmin"
+secret_access_key = "minioadmin"
+allow_insecure = true
+```
+
 ## Purge Drop Table Data
 
 Deletes data files of all dropped tables, freeing up storage space.