Credentials. Enrollment tokens let a machine join the cluster, so generate them one at a time and revoke any that leak.
Who it is forA platform engineer with spare servers, VMs or a rack who needs Spark capacity without moving data to a managed service.
The problemSpark jobs need more compute than one machine provides, and the team wants to use hardware it already owns.
The outcomeA Spark Standalone cluster built from enrolled machines, with a Spark runtime installed and jobs placed only on nodes where that runtime is ready.
What you need first
- Python and a Linux machine (the README says it runs end to end on Linux)
- Installation of the OLCF package as described in the README Install section
- For the multi-machine fabric: a Spark runtime installed with the JDK, and machines that can reach the control plane
- For the Fabric extension: a Fabric tenant you control, the olcf_fabric wheel in a Fabric Environment, and Entra and network setup
Steps
- Install a Spark runtime with
olcf runtime install --with-jdk. - Generate an enrollment token with
olcf worker enroll-token. - On each machine that should join, run
olcf-worker runwith the token. - Submit a test job to the cluster from the console or CLI and check that it runs on more than one worker.
Prompt for your agent
Use the open-lakehouse-compute-fabric repo (jddevtime/open-lakehouse-compute-fabric). Install the Spark runtime with `olcf runtime install --with-jdk`, enroll <number of machines> workers, and report the cluster members. Verify that a test job runs and that the worker list shows each machine as enrolled.
Caveat. The bundled development signing key is public, so re-sign the runtime with your own key before trusting a production installation.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page