Skip to content

Commit

Permalink
Clarify that spooling locations must not be shared
Browse files Browse the repository at this point in the history
  • Loading branch information
jhlodin committed Jan 7, 2025
1 parent 3c70f0c commit 1a4cfa6
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 5 deletions.
13 changes: 8 additions & 5 deletions docs/src/main/sphinx/admin/properties-client-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -154,11 +154,14 @@ Examples:
* `s3://my-spooling-bucket/my-segments/`

:::{caution}
When using the same object storage for spooling from multiple Trino clusters,
you must use separate locations for each cluster. For example:

* `s3://my-spooling-bucket/my-segments/cluster1`
* `s3://my-spooling-bucket/my-segments/cluster2`
The specified object storage location must not be used for spooling for another
Trino cluster or any object storage catalog. When using the same object storage
for multiple services, you must use separate locations for each one. For
example:

* `s3://my-spooling-bucket/my-segments/cluster1-spooling`
* `s3://my-spooling-bucket/my-segments/cluster2-spooling`
* `s3://my-spooling-bucket/my-segments/iceberg-catalog`
:::

### `fs.segment.ttl`
Expand Down
2 changes: 2 additions & 0 deletions docs/src/main/sphinx/client/client-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,8 @@ on a Trino cluster:
[](prop-protocol-spooling).
* Choose a suitable object storage that is accessible to your Trino cluster and
your clients.
* Create a location in your object storage that is not shared with any object
storage catalog or spooling for any other Trino clusters.
* Configure the object storage in `etc/spooling-manager.properties` using the
[](prop-spooling-file-system).

Expand Down

0 comments on commit 1a4cfa6

Please sign in to comment.