Globale Prozessregistrierung
Verwalten Sie globale Prozessnamen und finden Sie Prozesse in einem verteilten Erlang-Cluster, um koordinierte Abläufe zu ermöglichen
Globale Prozessregistrierung ist eine kostenlose Erlang OTP: Distributed & Fault-Tolerant Systems Programming-Lektion auf CoddyKit. Dies ist Lektion 3 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Erlang OTP: Distributed & Fault-Tolerant Systems Programming-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Erlang OTP: Distributed & Fault-Tolerant Systems Programming-Kurs umfasst insgesamt 4 Lektionen.
Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.
Global Names Across Nodes
In distributed Erlang, processes often need to find each other, even if they're on different machines. How do you find a process when you don't know which node it lives on?
Erlang's global module provides a solution: global process registration. It allows you to give a process a unique name that is known across all connected nodes in your cluster.
Local vs. Global Processes
Normally, when you register a process using register/2, its name is only known on the local node. If my_process is on nodeA@host, a process on nodeB@host can't find it just by its name.
Global registration solves this! It acts like a distributed directory service. Any process on any connected node can look up a globally registered name and get the corresponding Process ID (PID), regardless of where that process is running.
`global:register_name/2`
To make a process accessible globally, you use global:register_name(Name, Pid).
Name: An atom that will be the unique global name (e.g.,my_service).Pid: The Process ID of the process you want to register.
If the name is already taken, register_name returns {false, OldPid}, otherwise true. The global module ensures that a global name is unique across the entire distributed cluster.
`global:whereis_name/1`
Once a process is registered, any other process can find it using global:whereis_name(Name).
Name: The global name (atom) you're looking for.
This function returns the PID of the registered process if found, or the atom undefined if no process is registered under that name.
It's crucial to check for undefined before attempting to send messages to the returned PID.
Full Global Communication Demo
This runnable example brings it all together! A server process starts and registers itself globally. After a short delay, a client process then finds this global server and sends it a message, receiving a reply.
Observe how global:register_name ensures the server is known, and global:whereis_name allows the client to locate it, enabling seamless communication.
-module(global_demo).
-export([main/0]).
% Server Functions
server_init() ->
case global:register_name(my_global_service, self()) of
true ->
io:format("Server (~p) registered as my_global_service~n", [self()]),
server_loop();
{false, OldPid} ->
io:format("Error: my_global_service already registered by ~p~n", [OldPid])
end.
server_loop() ->
receive
{From, hello} ->
io:format("Server (~p) received 'hello' from ~p~n", [self(), From]),
From ! {self(), "Hi from server!"},
server_loop();
_ ->
io:format("Server (~p) received unknown message~n", [self()]),
server_loop()
end.
% Client Functions
client_task() ->
io:format("Client (~p) trying to find my_global_service...~n", [self()]),
case global:whereis_name(my_global_service) of
undefined ->
io:format("Client: my_global_service not found!~n");
ServerPid ->
io:format("Client: Found server ~p, sending 'hello'...~n", [ServerPid]),
ServerPid ! {self(), hello},
receive
{ServerPid, Response} ->
io:format("Client: Received response from server: '~s'~n", [Response])
after 5000 ->
io:format("Client: No response from server within 5 seconds.~n")
end
end.
% Main entry point
main() ->
% Start the server process
spawn(?MODULE, server_init, []),
timer:sleep(100), % Give server time to register
% Start the client process
spawn(?MODULE, client_task, []),
timer:sleep(2000). % Allow processes to run and communicateRemoving Global Names
When a globally registered process terminates, the global module automatically unregisters its name. However, you can also explicitly unregister a name using global:unregister_name(Name).
This is useful if you want to replace a service, or if a process needs to temporarily relinquish its global name. Remember, once unregistered, other processes can no longer find it by that name.
Handling Name Collisions
What happens if two different processes (even on different nodes) try to register the same global name?
The global module ensures that a global name is unique across the entire distributed system. The first process to successfully register the name wins. Subsequent attempts to register the same name will fail and return {false, OldPid}, indicating who already holds the name.
This prevents ambiguity and ensures that whereis_name/1 always returns a single, correct PID.
Practical Applications
Global process registration is ideal for implementing:
- Singleton Services: A single instance of a service (e.g., a configuration manager, a logger) accessible from anywhere.
- Resource Managers: A process responsible for managing a shared resource that multiple parts of your distributed system need to access.
- Entry Points: Providing a well-known name for the main entry point of a distributed application.
It simplifies process discovery in complex distributed architectures.
How Global Registration Works
The global module achieves its magic by maintaining a consistent view of registered names across all connected Erlang nodes.
When a name is registered, this information is broadcast to all other nodes. When a node connects or disconnects, the global module updates its internal state to reflect the current cluster topology and available global names.
This ensures that global:whereis_name/1 can quickly find the correct PID, no matter where it resides.
Global Registration Check
Consider a distributed Erlang system with two nodes, nodeA and nodeB, both connected. A process on nodeA successfully registers itself with global:register_name(my_service, self()).
What will happen if a process on nodeB then tries to call global:register_name(my_service, self())?
Global Names: A Distributed Directory
In this lesson, you learned about global process registration using Erlang's global module:
- It provides a way to assign unique names to processes that are discoverable across an entire distributed Erlang cluster.
global:register_name(Name, Pid)makes a process globally accessible.global:whereis_name(Name)allows any process on any connected node to find the PID associated with a global name.- The
globalmodule handles name uniqueness and automatically unregisters processes when they terminate, simplifying distributed process management.
Global names are fundamental for building robust, fault-tolerant, and discoverable services in distributed Erlang applications.
Häufig gestellte Fragen
Ist die Lektion „Globale Prozessregistrierung“ kostenlos?
Ja — der vollständige Text von „Globale Prozessregistrierung“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Erlang OTP: Distributed & Fault-Tolerant Systems Programming-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Erlang OTP: Distributed & Fault-Tolerant Systems Programming-Kurs umfasst insgesamt 4 Lektionen.
Was lerne ich in „Globale Prozessregistrierung“?
Verwalten Sie globale Prozessnamen und finden Sie Prozesse in einem verteilten Erlang-Cluster, um koordinierte Abläufe zu ermöglichen Du übst Erlang OTP: Distributed & Fault-Tolerant Systems Programming mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.
Brauche ich Erfahrung, um Erlang OTP: Distributed & Fault-Tolerant Systems Programming zu starten?
Keine Vorkenntnisse erforderlich. Erlang OTP: Distributed & Fault-Tolerant Systems Programming auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 3 von 4.
Wie lange dauert die Lektion „Globale Prozessregistrierung“?
Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.
Kann ich in dieser Erlang OTP: Distributed & Fault-Tolerant Systems Programming-Lektion Code schreiben und ausführen?
Ja. Jede Erlang OTP: Distributed & Fault-Tolerant Systems Programming-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.
Alle Lektionen in diesem Kurs
- Knotenkommunikation und Einrichtung
- Remote Procedure Calls (RPC)
- Globale Prozessregistrierung
- Sicherheit in verteilten Systemen und Cookies