# Alluxio Python Filesystem API based on FSSpec

{% hint style="warning" %}
This feature is experimental.
{% endhint %}

Alluxio Python SDK (`alluxiofs`) is based on [FSSpec](https://filesystem-spec.readthedocs.io/en/latest/api.html), which allows applications to seamlessly interact with various storage backends using a unified Python filesystem interface.It leverages a high-performance distributed caching layer, the Alluxio cluster, to significantly enhance data access speeds and reduce latency.This is particularly beneficial for data-intensive applications and workflows, especially AI training workloads, where large datasets need to be accessed quickly and repeatedly.

## Prerequisites

* A running Alluxio cluster
* Python's version >= 3.8

## Installation

### Install Dependencies

#### Install the underlying data lake storage(such as s3, oss)

Example: Deploy S3 as the underlying data lake storage [Install third-party S3 storage](https://s3fs.readthedocs.io/en/latest/)

```
pip install s3fs
```

#### Install alluxiofs

```
pip install alluxiofs
```

### Environment Setup

1. **Start an Alluxio cluster with at least 1 coordinator and 1 worker**

* If you want to start cluster in K8s, please refer to [Alluxio Official Documentation](https://documentation.alluxio.io/ee-ai-en/ai-3.5/start/install-alluxio-on-kubernetes).
* If you want to start cluster in Bare Metal, you can use `./bin/alluxio process start` cli.

2. **Configure Alluxio with the UFS's Credentials**

```
#s3 related
s3a.accessKeyId=your-s3a-accessKeyId
s3a.secretKey=your-s3a-secretKey


#oss related
fs.oss.accessKeyId=your-oss-keyid
fs.oss.accessKeySecret=your-oss-secert
fs.oss.endpoint=your-oss-endpoint
```

3. **Interacting with alluxio using alluxiofs**

For details，you can go to [Create alluxiofs's Instance](#create-alluxiofss-instance) and [alluxiofs's Basic File Operations](#alluxiofss-basic-file-operations).

## Load Data into Alluxio Cluster

If the data has already been loaded into the Alluxio cluster, skip this step.

This simple example creates a client to connects to an Alluxio cluster with ETCD membership in Kubernetes with service called `alluxio-etcd.alluxio-ai` with cluster\_name `alluxio` in namespace `alluxio-ai` and S3 as the under storage. See [advanced arguments to connect to Alluxio servers](#arguments-to-connect-to-alluxio-cluster) for more configuration settings.

Submit distributed load job to Alluxio cluster:

```
from alluxiofs.client import AlluxioClient

alluxio_client = AlluxioClient(cluster_name="alluxio", etcd_hosts="alluxio-etcd.alluxio-ai")
alluxio_client.submit_load("s3://bucket/path/to/dataset/")
```

This will trigger a load job asynchronously. You can wait until the load finishes or check the progress of this loading process using the following command:

```
alluxio_client.load_progress("s3://bucket/path/to/dataset/")
```

To cancel the distributed load job:

```
alluxio_client.stop_load("s3://bucket/path/to/dataset/")
```

## Create alluxiofs's Instance

This simple example creates a filesystem handler that connects to an Alluxio cluster with an ETCD membership in Kubernetes with service called `alluxio-etcd.alluxio-ai` with cluster\_name `alluxio` in namespace `alluxio-ai` and S3 as the under storage.

```
import fsspec
from alluxiofs import AlluxioFileSystem, setup_logger

# Register Alluxio to fsspec
fsspec.register_implementation("alluxiofs", AlluxioFileSystem, clobber=True)

# Create Alluxio filesystem
alluxio_options = {
    "alluxio.worker.page.store.page.size": "4MB",
}
alluxio_fs = fsspec.filesystem(
    "alluxiofs",
    cluster_name="alluxio",
    etcd_hosts="alluxio-etcd.alluxio-ai",
    target_protocol="s3",
    options=alluxio_options
    logger=setup_logger("./", level=logging.DEBUG),
)
```

See [advanced init arguments](#advanced-initialization-parameters) to set advanced arguments for Alluxio cluster and/or storage system connections.

## alluxiofs's Basic File Operations

```
# list files
contents = alluxio_fs.ls("s3://bucket/path/to/dataset/", detail=True)

# Read files
with alluxio_fs.open("s3://bucket/path/to/dataset/file1.parquet", "rb") as f:
    data = f.read()
```

More Python filesystem operations examples can be found [here](https://filesystem-spec.readthedocs.io/en/latest/usage.html#use-a-file-system).

## Integration with Other Frameworks

### Example: Ray

[Ray](https://www.ray.io/) is a fast and simple framework for building and running distributed applications. PyTorch, TensorFlow, and XGBoost trainers, running on top of Ray, can leverage Ray's advanced functionalities like creating heterogeneous clusters consisting of CPU machines for data loading and preprocessing, and GPU machines for training. Data loading, preprocessing, and training can be parallelized using Ray Data.

Trainers like PyTorch will read the same dataset again and again for each epoch. Getting a large dataset for PyTorch in each epoch becomes the training bottleneck. By leveraging Alluxio's high-performance distributed caching, trainers on Ray can reduce total training time, improve GPU utilization rate, and speed up the end-to-end model lifecycle.

Prerequisites: Ray version >= 2.8.2

```
# Pass the initialized Alluxio filesystem to Ray and read the dataset
ds = ray.data.read_parquet("s3://bucket/path/to/dataset/file1.parquet", filesystem=alluxio_fs)

# Get a count of the number of records in the single file
ds.count()

# Display the schema derived from the file header record
ds.schema()

# Display the header record
ds.take(1)

# Display the first data record
ds.take(2)

# Read multiple files:
ds2 = ray.data.read_parquet("s3://bucket/path/to/dataset/", filesystem=alluxio_fs)

# Get a count of the number of records in the files
ds2.count()
```

### Example: PyArrow

PyArrow allows applications and data to seamlessly connect with each other by providing a high-performance, in-memory columnar storage format. It enables efficient data interchange between different data processing systems. By delegating its storage interface to fsspec, PyArrow can access various storage backends through a unified interface. By using alluxiofs, PyArrow can leverage Alluxio's distributed caching capabilities to enhance data access speeds and reduce latency.

Example 1:

```
# Pass the initialized Alluxio filesystem to Pyarrow and read the data set from the example csv file
import pyarrow.dataset as ds
dataset = ds.dataset("s3://bucket/path/to/dataset/file1.parquet", filesystem=alluxio_fs)

# Get a count of the number of records in the file
dataset.count_rows()

# Display the schema derived from the file header record
dataset.schema

# Display the first record
dataset.take(0)
```

Example 2:

```
from pyarrow.fs import PyFileSystem, FSSpecHandler

# Create a python-based PyArrow filesystem using FsspecHandler
py_fs = PyFileSystem(FSSpecHandler(alluxio_fs))

# Read the data by using the Pyarrow filesystem interface
with py_fs.open_input_file("s3://bucket/path/to/dataset/file1.parquet") as f:
    f.read()
```

## Advanced Initialization Parameters

### Arguments to Connect to Alluxio Cluster

* **etcd\_hosts** (str, required): A comma-separated list of ETCD server hosts in the format "host1:port1,host2:port2,...". ETCD is used for dynamic discovery of Alluxio workers.
* **etcd\_port** (int, optional): The port number used by each ETCD server. Defaults to `2379`.
* **options** (dict, optional): A dictionary of Alluxio configuration options where keys are property names and values are property values. These options configure the Alluxio client behavior.

Example: Configure Alluxio fsspec. Note that the following options must be the same between alluxiofs and alluxio cluster

* `alluxio.worker.page.store.page.size` (default `1MB`): Size of each page in worker paged block store. Recommend to set to `20MB` for large parquet files.
* `alluxio.user.worker.selection.policy.consistent.hash.virtual.node.count.per.worker` (default `2000`): This is the number of virtual nodes for one worker in the consistent hashing algorithm. In a consistent hashing algorithm, on membership changes, some virtual nodes are re-distributed instead of rebuilding the whole hash table. This guarantees the hash table is changed only in a minimal. In order to achieve that, the number of virtual nodes should be X times the physical nodes in the cluster, where X is a balance between redistribution granularity and size. Recommend to set to `5`.

```
alluxio_options = {
    "alluxio.user.worker.selection.policy.consistent.hash.virtual.node.count.per.worker": "2000",
    "alluxio.worker.page.store.page.size": "4MB",
}
```

(Optional) Init `alluxio_client` for distributed load operations:

```
alluxio_client = AlluxioClient(etcd_hosts="host1,host2,host3", etcd_port=8888, options=alluxio_options)
```

Init `alluxio_fs` for fsspec filesystem operations:

```
alluxio_fs = fsspec.filesystem("alluxiofs", cluster_name="alluxio", etcd_hosts="alluxio-etcd.alluxio-ai", target_protocol="s3", options=alluxio_options)
```

config the logger of `alluxio_fs`

```
import logging
import fsspec
from alluxiofs import AlluxioFileSystem, setup_logger

alluxio_fs = fsspec.filesystem("alluxiofs", cluster_name="alluxio", etcd_hosts="alluxio-etcd.alluxio-ai", logger=setup_logger("./", level=logging.DEBUG))
```

### Arguments for storage backend

Arguments:

* **target\_protocol** (str, optional): Specifies the under storage protocol to create the under storage file system object. Common examples include `s3` for Amazon S3, `hdfs` for Hadoop Distributed File System, and others.
* **target\_options** (dict, optional): Provides a set of configuration options relevant to the `target_protocol`. These options might include credentials, endpoint URLs, and other protocol-specific settings required to successfully interact with the under storage system.
* **fs** (object, optional): Directly supplies an instance of a file system object for accessing the underlying storage of Alluxio
* **logger**(object， optional): config the the path to store log files and level of logger, the path is the current path default, and the level is logging.INFO default.

#### Example: connect to S3

To connect to S3, you can follow these steps:

1. Review S3 fsspec documentation: Refer to the [s3fs documentation](https://s3fs.readthedocs.io/en/latest/) to find out the supported arguments for connecting to S3. Typical arguments include:

* **anon** bool (False): Whether to use anonymous connection (public buckets only). If False, uses the key/secret given, or boto's credential resolver; client\_kwargs, environment, variables, config files, EC2 IAM server, in that order
* **endpoint\_url** string (None): Use this endpoint\_url, if specified. Needed for connecting to non-AWS S3 buckets. Takes precedence over `endpoint_url` in client\_kwargs.
* **key** string (None): If not anonymous, use this access key ID, if specified. Takes precedence over `aws_access_key_id` in client\_kwargs.
* **secret** string (None): If not anonymous, use this secret access key, if specified. Takes precedence over `aws_secret_access_key` in client\_kwargs.
* **token** string (None): If not anonymous, use this security token, if specified

2. Pass the supported arguments as target\_options to Alluxio: You can then use these arguments to create an Alluxio file system object using fsspec.

Here's how to create an Alluxio file system object connected to S3 using fsspec:

```
import fsspec

# Example configuration for connecting to S3
s3_options = {
    "key": "your-aws-access-key",
    "secret": "your-aws-secret-key",
    "endpoint_url": "https://s3.your-endpoint.com"
}

# Creating the Alluxio file system object
alluxio_fs = fsspec.filesystem(
    "alluxiofs",
    cluster_name="alluxio",
    etcd_hosts="alluxio-etcd.alluxio-ai",
    target_protocol="s3",
    target_options=s3_options
)

# Now you can use alluxio_fs to interact with the Alluxio file system backed by S3
```

In this example:

* Replace `your-aws-access-key` and `your-aws-secret-key` with your actual AWS credentials.
* Replace `https://s3.your-endpoint.com` with the appropriate endpoint URL for your S3-compatible service if needed.

By following these steps, you can effectively connect to Alluxio with an S3 backend using fsspec.

## Monitoring Metrics

### Monitoring System Setup

1. **Prometheus Installation and Configuration**\
   Edit the `prometheus.yml` configuration file and then start Prometheus:

   ```bash
   nohup ./prometheus --web.enable-admin-api --config.file=./prometheus.yml >./prometheus.log 2>&1 &
   ```
2. **Grafana Installation and Configuration**\
   Start Grafana:

   ```bash
   nohup ./bin/grafana-server --homepath . web >./grafana.log 2>&1 &
   ```

For more detailed instructions on setting up the monitoring system, refer to the [Alluxio Official Documentation](https://documentation.alluxio.io/ee-ai-en/ai-3.5/start/monitoring-and-metrics).

### Explanation of Monitoring Metrics

| **Metric Name**                             | **Description**                                                                    | **Labels**          | **Unit**          | **Implementation Code** |
| ------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------- | ----------------- | ----------------------- |
| `alluxio_http_server_call_latency_ms`       | Histogram of HTTP service call latency (Bucket boundaries: \[10, 40, 160, 640] ms) | `method`, `success` | Milliseconds (ms) | `HistogramWrapper`      |
| `alluxio_http_server_result_total`          | Total count of HTTP service results                                                | `method`, `state`   | Count             | `CounterWrapper`        |
| `alluxio_http_server_call_latency_ms_sum`   | Total latency of HTTP service calls                                                | `method`, `success` | Milliseconds (ms) | `HistogramWrapper`      |
| `alluxio_http_server_call_latency_ms_count` | Count of HTTP service calls                                                        | `method`, `success` | Count             | `HistogramWrapper`      |
