Found this acronym in the docs of Ray Core, used for its main API server:
[..] the head node needs to open several more ports:
--port: Port of Ray (GCS server). The head node will start a GCS server listening on this port. Default: 6379.
Found this acronym in the docs of Ray Core, used for its main API server:
[..] the head node needs to open several more ports:
--port: Port of Ray (GCS server). The head node will start a GCS server listening on this port. Default: 6379.
The Ray 1.0 Architecture Whitepaper says GCS stands for "Global Control Store". Ray 2.0 was just released, which brought a lot of breaking changes. I believe GCS might change in the Ray 2.0 Architecture Whitepaper to mean "Global Control Service" to better encapsulate what it is, but the gist is the same :)
In Ray 2.0 it's called the Global Control Service. In 1.0 it was Global Control Store. It basically manages a cluster (there's exactly one inside each cluster) and runs on the cluster's head node. It's written in C++ and has been actively developed since 2017.
Relevant docs from the 2.0 whitepaper
One of the worker nodes is designated as the head node. In addition to the above processes, the head node also hosts: The Global Control Service (GCS). The GCS is a server that manages cluster-level metadata, such as the locations of actors, stored as key-value pairs that may be cached locally by workers. The GCS also manages a handful of cluster-level operations, including scheduling for placement groups and actors and determining cluster node membership. In general, the GCS manages metadata that is less frequently accessed but likely to be used by most or all workers in the cluster. This is to ensure that GCS performance is not critical to application performance. GCS fault tolerance is new in Ray 2.0, allowing the GCS to run on any and multiple nodes, instead of a designated head node.
The Global Control Store is now known as the Global Control Service (GCS) and features a completely updated design to simplify coordination and reliability.
The Global Control Service, also known as the GCS, is Ray’s cluster control plane. It manages the Ray cluster and serves as a centralized place to coordinate raylets and discover other cluster processes. The GCS also serves as an entry point for external services like the autoscaler and dashboard to communicate with the Ray cluster. The GCS is currently single-threaded except for heartbeat checks and resource polling; there are ongoing efforts to scale other operations such as actor management via multithreading.
© 2022 - 2024 — McMap. All rights reserved.