전역 프로세스 등록
전역 프로세스 이름을 관리하고 분산 Erlang 클러스터에서 프로세스를 검색하여 작업을 조정합니다.
전역 프로세스 등록은(는) CoddyKit의 무료 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Erlang OTP: Distributed & Fault-Tolerant Systems Programming 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
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.
AI 튜터와 함께 Erlang을(를) 배우세요 — 무료
브라우저에서 실제 코드를 작성하고 실행하며, 24/7 AI 튜터로부터 즉각적인 도움을 받고, 웹이나 앱에서 중단한 부분부터 계속 학습하세요.
- 코스
- 12
- 레슨
- 48
자주 묻는 질문
“전역 프로세스 등록” 강의는 무료인가요?
네 — “전역 프로세스 등록” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 강의 전체를 잠금 해제할 수 있습니다. Erlang OTP: Distributed & Fault-Tolerant Systems Programming 강의에는 총 4개의 강의가 포함되어 있습니다.
“전역 프로세스 등록”에서 뭘 배우나요?
전역 프로세스 이름을 관리하고 분산 Erlang 클러스터에서 프로세스를 검색하여 작업을 조정합니다. 브라우저에서 직접 실행하는 실습 코드로 Erlang OTP: Distributed & Fault-Tolerant Systems Programming을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Erlang OTP: Distributed & Fault-Tolerant Systems Programming을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Erlang OTP: Distributed & Fault-Tolerant Systems Programming은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.
“전역 프로세스 등록” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- 노드 통신 및 설정
- 원격 프로시저 호출(RPC)
- 전역 프로세스 등록
- 분산 보안과 쿠키