# Installer alluxio avec Homebrew Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de alluxio pour les workflows d'agents IA. ## installation ```sh sudo av install brew:alluxio ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install alluxio ``` Preuve: local Homebrew formula metadata ## Faits du paquet - **Clé du paquet:** brew:alluxio - **Gestionnaire de paquets:** Homebrew - **Version:** 2.9.5 - **Résumé source:** Open Source Memory Speed Virtual Distributed Storage - **Page d'accueil:** - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - alluxio (alias) - alluxio-common.sh (alias) - alluxio-masters.sh (alias) - alluxio-monitor.sh (alias) - alluxio-mount.sh (alias) - alluxio-start.sh (alias) - alluxio-stop.sh (alias) - alluxio-workers.sh (alias) - launch-process (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 2.9.5 ## Historique du projet et usages Alluxio is an open source data orchestration and virtual distributed storage system. It sits between compute frameworks and storage systems, presenting a unified namespace and APIs while caching data close to analytics and AI workloads. ### Historique du projet The Alluxio README states that the project was formerly known as Tachyon and originated as a UC Berkeley AMPLab research project. It was the data layer of the Berkeley Data Analytics Stack, and the README points readers to Haoyuan Li's dissertation, Alluxio: A Virtual Distributed File System, for the research background. The project later became Alluxio, an Apache-licensed open source system owned by the Alluxio Open Source Foundation and managed by an Alluxio Project Management Committee. Official docs position it as data orchestration technology for analytics and AI, with a memory-first tiered architecture, global namespace, and server-side API translation. ### Historique d'adoption Official documentation says Alluxio has attracted more than 1000 contributors from over 300 institutions including Alibaba, Baidu, CMU, Google, IBM, Intel, NJU, Red Hat, Tencent, UC Berkeley, and Yahoo. It also says the project is deployed in production by hundreds of organizations, while the README describes petabyte-scale production deployments and a largest deployment exceeding thousands of nodes. Alluxio adoption followed the data-platform pattern of being useful when compute and storage are decoupled. Its docs call out use with Apache Spark, Presto, Tensorflow, Apache HBase, Apache Hive, and Apache Flink above storage systems such as Amazon S3, Google Cloud Storage, OpenStack Swift, HDFS, IBM Cleversafe, EMC ECS, Ceph, NFS, Minio, and Alibaba OSS. ### Modes d'utilisation Operators deploy an Alluxio master and workers, mount persistent under storage into the Alluxio namespace, and point compute jobs at Alluxio through HDFS-compatible, S3, FUSE/POSIX, REST, or Java APIs. The Spark guide, for example, shows Spark applications reading and writing `alluxio://` paths while Alluxio transparently fetches and caches data from under storage. The command-line package includes administrative and cluster scripts such as `alluxio`, `alluxio-start.sh`, `alluxio-stop.sh`, `alluxio-masters.sh`, and `alluxio-workers.sh`. In package-manager terms this is not just a CLI utility; it is a local entry point into a distributed service stack. ### Pourquoi les passionnés de paquets s'y intéressent Alluxio is significant to package people because it packages a full distributed Java data system behind Unix-style scripts. A Homebrew install can be convenient for development and local testing, but production use usually involves clusters, Docker, Kubernetes, Hadoop/Spark classpaths, and configuration files. The former Tachyon name, AMPLab origin, and BDAS connection tie Alluxio to the same research-to-production wave that shaped Spark-era big data infrastructure. Its package metadata has to communicate storage, cache, filesystem, and orchestration at once because all of those labels are true in different deployment modes. ### Chronologie - Tachyon era: Project originated at UC Berkeley AMPLab as the data layer of the Berkeley Data Analytics Stack. - Alluxio rename: The project became Alluxio, described by the README as formerly known as Tachyon. - Foundation/PMC era: README states the Alluxio Open Source Foundation owns the project and the PMC manages operation. - Current: Official docs position Alluxio as data orchestration for analytics and AI across many compute engines and storage backends. ### Related projects - Apache Spark, Presto, Tensorflow, Apache HBase, Apache Hive, and Apache Flink are documented compute-side integrations. - Amazon S3, Google Cloud Storage, OpenStack Swift, HDFS, IBM Cleversafe, EMC ECS, Ceph, NFS, Minio, and Alibaba OSS are documented storage-side examples. - The Berkeley Data Analytics Stack and UC Berkeley AMPLab are central to Alluxio's origin story. ### Sources - - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ${alluxio.conf.dir}/alluxio-site.properties, ${user.home}/.alluxio/alluxio-site.properties, /etc/alluxio/alluxio-site.properties ## Combined YAML source View the package source record on GitHub. [combined/alluxio.yml](https://github.com/mxcl/pkgdb/blob/main/combined/alluxio.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph