-
-
Notifications
You must be signed in to change notification settings - Fork 0
Plain language glossary
A standard Minecraft area that is 16 blocks wide and 16 blocks long. The world is stored and processed in many chunks.
A Java world storage file that can contain up to 32 by 32 chunks. Its filename ends in .mca.
One Minecraft server process in the planned Elah system. A worker would be responsible for one or more parts of the world.
A physical computer or virtual machine that can run one or more workers.
The planned unit of responsibility in Elah. A cell contains a group of world storage areas. Exactly one worker should be allowed to authoritatively change an active cell.
The worker that currently has permission to make authoritative changes to a cell.
A number that increases when responsibility changes. An old worker with an old number can be rejected instead of accidentally changing current data.
The planned process for moving a player's authoritative state from one worker to another as the player crosses a boundary.
The part that manages workers, health, ownership, and administrative decisions. Normal player movement and gameplay traffic should not pass through it.
The planned Elah scheduler. Shepherd would decide where Minecraft cells belong by combining ownership, topology, gameplay pressure, machine capacity, and operator rules.
A future adapter that can report capacity and start, inspect, drain, or stop workers using native processes, Docker, or an external infrastructure system. It cannot assign cell ownership.
A COLD worker is not running. A WARM worker is ready but owns no cells. A HOT worker actively owns and serves one or more cells.
Guaranteed capacity is reserved for a cluster. Burst capacity is shared spare capacity available up to a limit. Preemptible capacity is temporary capacity that may be reclaimed after Elah safely drains its cells.
Hard limits on the workers and infrastructure resources one cluster may consume. It is a scheduling boundary, not a bill.
A pool of machines and available capacity. It does not own Minecraft cells or worlds.
Several separate Elah clusters using one infrastructure fleet while keeping their identities, credentials, worlds, storage, networks, metrics, and ownership authority isolated.
Elah's main planned system. It divides one logical Minecraft world into cells and coordinates their owners safely across workers.
A future idea for placing whole independent Minecraft servers across machines. Those servers would not be parts of one distributed world. This mode is not implemented and has no assigned release.
Stop without producing a trusted result when safety cannot be proven. For example, Observer produces no report if the world changes during its scan.
A dangerous situation where two machines both believe they are the authoritative owner of the same data.
A stable point-in-time view of files. A snapshot lets a tool inspect data without the files changing underneath it.
An independent implementation used in tests to check that Elah's result agrees with separately known facts. The Observer Laboratory uses pinned PrismarineJS tools as a development-only oracle.
Elah 0.0.3 | Repository | Releases | Security