RetryFlow wraps a flow with context and allows to individually retry elements. A decider function decides if another try should be made and gives the element to try with.
Retries are backed off exponentially.
Retries are limited by maxRetries.
Inspired by the work of Gilad Hoch <gilad.hoch@thomsonreuters.com> and Martynas Mickevičius <self@2m.lt>
* backport from Classic
* the scenario was that the snapshot was kept but the journal was
entirely deleted, and then it should anyway write next event
with the sequence number from the snapshot
* doesn't look like the EventSourcedBehavior had this problem,
but doesn't hurt to use the max
Re-uses the code from the migration guide as the mgiration logic
is in adapters.
Almost seems very obvious you can do this but can't hurt to have.
* Apply suggestions from code review
Co-Authored-By: Helena Edelson <helena@users.noreply.github.com>
* add withDataCenter in Entity, following same patterna as the role
* update cluster-dc.md, split in classic and new pages
* fix bug in ClusterSharding shouldHostShard
* contains on String
* update multi-dc singleton sample
When we use [] around the level it adds a space which then means
searching for [INFO] doesn't work. Left it in for the examples
that don't surround logger with []
* Initialize logging things together. Save 2 fields in ActorContextAdapter (if logging isn't used)
* Dealt with bincomp by handcoding things in Deploy.
* Pass tags in remote deploy messages (serialization)
* Docs plus signature that works for Java API
* Allow tags to be empty or else we can't create an `.empty`
* some cluster logging improvements
* most logger names are actually good, when using ActorLogging since
config can be setup on the package (prefix)
* override logSource when StageLogging is used
* replace system.log with more specific logger
* lastSequenceNr should reflect the snapshot sequence number and not start
at 0 when there was no journal to begin with.
* Use LevelDBJournal in Test Case
The test case now properly simulates a recovery from a snapshot without
a journal.
(cherry picked from commit df2a1d8a52e13aa09edd20bcf95ff617cd7acf9c)
* good to make it more strict in Akka 2.6.0
* possibility to opt out via config
* migration guide
* clarification of why
* don't mention opt-out in migration guide because it shouldn't be abused
