Restore accidental code removal

Author: etolbakov

docs/src/main/sphinx/admin/fault-tolerant-execution.md

@@ -71,6 +71,11 @@ execution on a Trino cluster:
     fault-tolerant execution and typically only to deactivate with `NONE`, since
     switching between modes on a cluster is not tested.
   - `NONE`
+* - `retry-policy.allowed`
+  - List of retry policies that are allowed to be configured for a cluster.
+    This property is used to prevent a user from configuring a retry policy that
+    is not meant to be used on the given cluster.
+  - `NONE`, `QUERY`, `TASK` 
 * - `exchange.deduplication-buffer-size`
   - [Data size](prop-type-data-size) of the coordinator's in-memory buffer used
     by fault-tolerant execution to store output of query
@@ -382,7 +387,7 @@ fault-tolerant execution. You can configure a filesystem-based exchange manager
 that stores spooled data in a specified location, such as {ref}`AWS S3
 <fte-exchange-aws-s3>` and S3-compatible systems, {ref}`Azure Blob Storage
 <fte-exchange-azure-blob>`, {ref}`Google Cloud Storage <fte-exchange-gcs>`,
-or {ref}`HDFS <fte-exchange-hdfs>`.
+{ref}`Alluxio <fte-exchange-alluxio>`, or {ref}`HDFS <fte-exchange-hdfs>`.
 
 ### Configuration
 
@@ -508,6 +513,18 @@ the property may be configured for:
     retry a request.
   - `10`
   - Azure Blob Storage
+* - `exchange.alluxio.block-size`
+  - Block [data size](prop-type-data-size) for Alluxio storage.
+  - `4MB`
+  - Alluxio
+* - `exchange.alluxio.site-file-path`
+  - Path to the alluxio site file that contains your custom configuration,
+    for example `/etc/alluxio-site.properties`. The file must exist on all
+    nodes in the Trino cluster. Follow the [Alluxio client configuration
+    documentation](https://docs.alluxio.io/os/user/stable/en/operation/Configuration.html)
+    for more details.
+  -
+  - Alluxio
 * - `exchange.hdfs.block-size`
   - Block [data size](prop-type-data-size) for HDFS storage.
   - `4MB`
@@ -601,6 +618,18 @@ exchange.s3.endpoint=https://storage.googleapis.com
 exchange.gcs.json-key-file-path=/path/to/gcs_keyfile.json
 ```
 
+(fte-exchange-alluxio)=
+#### Alluxio
+
+The following `exchange-manager.properties` configuration example specifies Alluxio
+as the spooling storage destination.
+
+```properties
+exchange-manager.name=alluxio
+exchange.base-directories=alluxio://alluxio-master:19998/exchange-spooling-directory
+exchange.alluxio.site-file-path=/path/to/alluxio-site.properties
+```
+
 (fte-exchange-hdfs)=
 #### HDFS