Strategie avanzate di riavvio
Approfondisca le strategie di riavvio one_for_one, one_for_all e rest_for_one, comprendendone le implicazioni per la tolleranza ai guasti
Strategie avanzate di riavvio è una lezione Erlang OTP: Distributed & Fault-Tolerant Systems Programming gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Erlang OTP: Distributed & Fault-Tolerant Systems Programming, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Erlang OTP: Distributed & Fault-Tolerant Systems Programming include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Intro to Restart Strategies
Welcome to a crucial topic in Erlang: restart strategies! These define how a supervisor reacts when one of its child processes crashes.
Understanding these strategies is key to building fault-tolerant and self-healing systems, which is a hallmark of Erlang/OTP.
Supervisors: The Fault Managers
Before diving in, let's quickly recap: a supervisor is a special process that monitors other processes (its children).
- If a child process dies, the supervisor detects it.
- Based on its configured restart strategy, the supervisor decides how to bring the system back to a healthy state.
- This ensures your application can recover from individual process failures automatically.
`one_for_one`: Isolated Restarts
The one_for_one strategy is the simplest and most common. When a child process terminates:
- Only the failing child process is restarted.
- All other sibling processes remain unaffected and continue running.
This strategy is ideal for systems where child processes are largely independent of each other, such as individual client connections.
`one_for_one` in Action
Let's see one_for_one. We'll have a supervisor managing a single worker. When the worker crashes, only it restarts.
To run:
1. Compile: c(worker_gen). c(supervisor_one_for_one).
2. Start supervisor: supervisor_one_for_one:start_link().
3. Crash worker: worker_gen:crash(worker_1).
Observe the output in your Erlang shell.
-module(worker_gen).
-behaviour(gen_server).
-export([start_link/1, init/1, handle_call/3, terminate/2, crash/1]).
start_link(Id) ->
gen_server:start_link({local, Id}, ?MODULE, Id, []).
init(Id) ->
io:format("Worker ~p (~p) started.~n", [Id, self()]),
{ok, Id}.
handle_call(crash, _From, State) ->
exit(i_crashed),
{reply, ok, State};
handle_call(_Req, _From, State) ->
{reply, ok, State}.
terminate(_Reason, Id) ->
io:format("Worker ~p (~p) terminated.~n", [Id, self()]).
crash(Id) ->
gen_server:call(Id, crash).
-module(supervisor_one_for_one).
-behaviour(supervisor).
-export([start_link/0, init/1]).
start_link() ->
supervisor:start_link({local, ?MODULE}, ?MODULE, []).
init([]) ->
ChildSpec = #{
id => worker_1,
start => {worker_gen, start_link, [worker_1]},
restart => permanent,
shutdown => 5000,
type => worker,
modules => [worker_gen]
},
{ok, #{
strategy => {one_for_one, 3, 5},
children => [ChildSpec]
}}.
`one_for_all`: All for One Failure
The one_for_all strategy takes a more drastic approach:
- If any child process terminates, all other child processes are first terminated.
- Then, all child processes (including the one that crashed) are restarted.
This is useful when your child processes are tightly coupled and require a consistent, synchronized state. A failure in one implies a need to reset the entire group.
`one_for_all` in Action
Here, a supervisor manages two workers. Crash one, and both will restart.
To run:
1. Compile: c(worker_gen). c(supervisor_one_for_all).
2. Start supervisor: supervisor_one_for_all:start_link().
3. Crash worker: worker_gen:crash(worker_A).
Notice how both worker_A and worker_B restart.
-module(worker_gen).
-behaviour(gen_server).
-export([start_link/1, init/1, handle_call/3, terminate/2, crash/1]).
start_link(Id) ->
gen_server:start_link({local, Id}, ?MODULE, Id, []).
init(Id) ->
io:format("Worker ~p (~p) started.~n", [Id, self()]),
{ok, Id}.
handle_call(crash, _From, State) ->
exit(i_crashed),
{reply, ok, State};
handle_call(_Req, _From, State) ->
{reply, ok, State}.
terminate(_Reason, Id) ->
io:format("Worker ~p (~p) terminated.~n", [Id, self()]).
crash(Id) ->
gen_server:call(Id, crash).
-module(supervisor_one_for_all).
-behaviour(supervisor).
-export([start_link/0, init/1]).
start_link() ->
supervisor:start_link({local, ?MODULE}, ?MODULE, []).
init([]) ->
Child1 = #{
id => worker_A,
start => {worker_gen, start_link, [worker_A]},
restart => permanent, shutdown => 5000, type => worker, modules => [worker_gen]
},
Child2 = #{
id => worker_B,
start => {worker_gen, start_link, [worker_B]},
restart => permanent, shutdown => 5000, type => worker, modules => [worker_gen]
},
{ok, #{
strategy => {one_for_all, 3, 5},
children => [Child1, Child2]
}}.
`rest_for_one`: Cascade Restarts
The rest_for_one strategy offers a middle ground:
- If a child process terminates, it and all subsequent children (those defined after it in the supervisor's child list) are terminated.
- Then, the failed child and all subsequent children are restarted.
- Children defined before the failed child are left untouched.
This is useful when processes have sequential dependencies, where a failure in an earlier stage might invalidate the state of later stages.
`rest_for_one` in Action
We have three workers: X, Y, Z. If Y crashes, Y and Z restart, but X remains active.
To run:
1. Compile: c(worker_gen). c(supervisor_rest_for_one).
2. Start supervisor: supervisor_rest_for_one:start_link().
3. Crash worker: worker_gen:crash(worker_Y).
See worker_X stay running, while worker_Y and worker_Z restart.
-module(worker_gen).
-behaviour(gen_server).
-export([start_link/1, init/1, handle_call/3, terminate/2, crash/1]).
start_link(Id) ->
gen_server:start_link({local, Id}, ?MODULE, Id, []).
init(Id) ->
io:format("Worker ~p (~p) started.~n", [Id, self()]),
{ok, Id}.
handle_call(crash, _From, State) ->
exit(i_crashed),
{reply, ok, State};
handle_call(_Req, _From, State) ->
{reply, ok, State}.
terminate(_Reason, Id) ->
io:format("Worker ~p (~p) terminated.~n", [Id, self()]).
crash(Id) ->
gen_server:call(Id, crash).
-module(supervisor_rest_for_one).
-behaviour(supervisor).
-export([start_link/0, init/1]).
start_link() ->
supervisor:start_link({local, ?MODULE}, ?MODULE, []).
init([]) ->
ChildA = #{
id => worker_X,
start => {worker_gen, start_link, [worker_X]},
restart => permanent, shutdown => 5000, type => worker, modules => [worker_gen]
},
ChildB = #{
id => worker_Y,
start => {worker_gen, start_link, [worker_Y]},
restart => permanent, shutdown => 5000, type => worker, modules => [worker_gen]
},
ChildC = #{
id => worker_Z,
start => {worker_gen, start_link, [worker_Z]},
restart => permanent, shutdown => 5000, type => worker, modules => [worker_gen]
},
{ok, #{
strategy => {rest_for_one, 3, 5},
children => [ChildA, ChildB, ChildC]
}}.
Selecting the Best Strategy
Choosing the right strategy depends on your application's architecture and process dependencies:
one_for_one: Use for independent processes, like individual client connections or request handlers.one_for_all: Best for tightly coupled processes that must always be in a consistent state together (e.g., a group of processes managing a single resource).rest_for_one: Suitable for sequential pipelines or layered systems where a failure in an earlier stage affects subsequent stages.
Test Your Knowledge
You are building a system where a primary worker fetches data, and two secondary workers process different aspects of that data. If the primary worker fails, the secondary workers cannot continue with stale data and must also restart. If a secondary worker fails, the others are unaffected. Which strategy is most appropriate for the primary worker and its dependent secondary workers?
Recap: Mastering Restarts
You've explored Erlang's powerful restart strategies:
one_for_one: Restarts only the failed child, keeping others running.one_for_all: Restarts all children if any one fails, ensuring full consistency.rest_for_one: Restarts the failed child and all subsequent children in the list.
These strategies are fundamental to building robust, self-healing applications in Erlang, allowing your system to recover from failures gracefully.
Domande Frequenti
La lezione «Strategie avanzate di riavvio» è gratuita?
Sì — il testo completo di «Strategie avanzate di riavvio» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Erlang OTP: Distributed & Fault-Tolerant Systems Programming, passa a CoddyKit PRO. Il corso Erlang OTP: Distributed & Fault-Tolerant Systems Programming include 4 lezioni in totale.
Cosa imparerò in «Strategie avanzate di riavvio»?
Approfondisca le strategie di riavvio one_for_one, one_for_all e rest_for_one, comprendendone le implicazioni per la tolleranza ai guasti Eserciti Erlang OTP: Distributed & Fault-Tolerant Systems Programming con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare Erlang OTP: Distributed & Fault-Tolerant Systems Programming?
Non è richiesta alcuna esperienza precedente. Erlang OTP: Distributed & Fault-Tolerant Systems Programming su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Strategie avanzate di riavvio»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione Erlang OTP: Distributed & Fault-Tolerant Systems Programming?
Sì. Ogni lezione Erlang OTP: Distributed & Fault-Tolerant Systems Programming include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Alberi di supervisione complessi
- Gestione dinamica dei processi
- Strategie avanzate di riavvio
- Bridge dei supervisor e gerarchie di processi miste