I'm seeing a scenario where a cluster member is killed by Marathon due to
out of control memory growth because a persistent actor stops processing
message. When Marathon kills the cluster member the cluster role doesn't
recover due to the shard coordinators having issue. My log is full
Your understanding is correct, it should not read after recovery. One
reason could be that actors are restarted or stopped/started due to
exceptions.
/Patrik
ons 11 jan. 2017 kl. 19:11 skrev Richard Ney :
> My team is in pre-production and were chasing some odd behaviors
I'll admit that it is in fact working as expected - apologies.
To recap the pieces relating to the fact I'm using assembly jars with
external configuration files:
- exclude the config files from the assembly jars using sbt-assembly
On 12/01/2017 19:07, Rafał Krzewski wrote:
Of course all this is moot if said tool already exist, and you are
now trying to tweak Akka to produce event log in suitable format :)
That's the use case - JSON text files containing a sequence of events
are the desired output. Being able to use
Hi Alan,
I remember someone suggesting using a RDBMS as the store for similar use
case.
For example you could
take https://github.com/okumin/akka-persistence-sql-async plugin to write
the messages to PostgreSQL, but declare the message and snapshot columns in
the tables as JSONB rather than
Hi Rafał,
Thank you very much!
Cheers,
Sergey
четверг, 12 января 2017 г., 12:51:23 UTC+2 пользователь Rafał Krzewski
написал:
>
> Hi,
>
> here's more robust implementation of stream splitter, based on Partition
> stage: https://gist.github.com/rkrzewski/a0fc5d0b47d9a3e0b2c81435adef3fe7
>
>
Ok after reading the documentation which says :
*The supervisor itself is supervised by the top-level actor provided by
the ActorSystem, which has the default policy to restart in case of
all Exception cases (with the notable exceptions
of ActorInitializationException and
I have some fairly non-standard requirements for a persistence plugin
for a long-running lo-event-rate simulation - I can assume a shared
filesystem, the event rates will be low (10/sec max) and I'd like to use
the persistence files with external tools to analyse the event stream
from outside
On Thu, Jan 12, 2017 at 2:31 PM, Kilic Ali-Firat
wrote:
>
> override def supervisorStrategy: SupervisorStrategy =
> OneForOneStrategy(maxNrOfRetries = 10, withinTimeRange = 1 minutes) {
> case _ : Exception => Resume
> }
>
The supervision strategy must be
So I investigated running the app with -Dakka.log-config-on-start=on.
I couldn't get any associated config output until I reverted log.conf to
use the default logger:
akka {
log-config-on-start=on
log-dead-letters = 0
log-dead-letters-during-shutdown = off
Hi,
here's more robust implementation of stream splitter, based on Partition
stage: https://gist.github.com/rkrzewski/a0fc5d0b47d9a3e0b2c81435adef3fe7
cheers,
Rafał
W dniu środa, 11 stycznia 2017 20:26:24 UTC+1 użytkownik Sergey Sopin
napisał:
>
> Hi again,
>
> Rafał, could you please give me
run the app with -Dakka.log-config-on-start=on
On Thu, Jan 12, 2017 at 11:15 AM, vacuumstate
wrote:
> Hi,
>
> I'm having trouble trying to get logging working as per standard akka
> documentation.
>
> The application consists of several scala/sbt assembly jars deployed
Hi,
I'm having trouble trying to get logging working as per standard akka
documentation.
The application consists of several scala/sbt assembly jars deployed to a
'bin' folder along with their *.conf HOCON and logback.xml files (which are
excluded from the assembly packaging).
The issue is
13 matches
Mail list logo