can someone explain the difference between the "supervisor"- and the "try-catch"-error handling strategies in an ActorSystem in Scala?
Scala - Difference between Supervisor and Try-catch error handling strategies
141 Views Asked by Dave At
1
There are 1 best solutions below
Related Questions in SCALA
- Add additional fields to Linq group by
- couldn't copy pdb file to another directory while consuming wcf web service
- Why are the aliases for string and object in lowercase?
- WPF MessageBox Cancel checkbox check
- Resolve object using DI container with object instance
- Creating a parametrized field name for a SELECT clause
- Does compiler optimize operation on const variable and literal const number?
- Get data from one form to another form in C#
- Writing/Overwriting to specific XML file from ASP.NET code behind
- Deleting Orphans with Fluent NHibernate
Related Questions in ACTORSYSTEM
- Add additional fields to Linq group by
- couldn't copy pdb file to another directory while consuming wcf web service
- Why are the aliases for string and object in lowercase?
- WPF MessageBox Cancel checkbox check
- Resolve object using DI container with object instance
- Creating a parametrized field name for a SELECT clause
- Does compiler optimize operation on const variable and literal const number?
- Get data from one form to another form in C#
- Writing/Overwriting to specific XML file from ASP.NET code behind
- Deleting Orphans with Fluent NHibernate
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Try-catch can recover from
Exception
thrown within thetry
block (provided that error is reported by throwingException
). It isn't tied to actors but it's an available method of dealing with errors in Scala (inherited from Java):Supervisor is used to decide what to do if
Exception
in our code wasn't caught or if some other error happened - which usually means some otherException
but not thrown nor handled by our code - transporting message from one cluster to another, invalid internal state, etc.Try-catch is something you can use inside your own code to make sure that a method will succeed. It's very local in scope. If you cannot make such guarantee and want to tell ActorSystem what to do with an
Actor
that couldn't handle error on its own (or maybe even with a whole group ofActor
s) then you use Supervisor - Supervisor however cannot just catchException
and make sure that function will return normal value instead. It will order Actor to restart (with clearing its state or with keeping the current state), kill Actor permanently or escalate to Actor's parent.When supervision is needed is quite well explained in the documentation.
Simplifying, dealing with errors on processing should be left for Actor, which internaly recovers from errors using
try
-catch
,Try
, etc, while Supervisor should be used with SupervisionStrategies to provide fault-tolerance like in documentation.