Hi,
I have defined a publisher actor and subscriber actor. How could I know if
the stream has been completed from the outside (where I create the stream)?
Thanks for your help.
Guofeng
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>
Thank you Patrik!
On Saturday, September 24, 2016 at 10:10:03 AM UTC-7, Patrik Nordwall wrote:
>
> Take a look at MergeHub. It's rather new.
> http://doc.akka.io/docs/akka/2.4/scala/stream/stream-dynamic.html
>
> /Patrik
> lör 24 sep. 2016 kl. 00:53 skrev oleksiys >:
>
>> Hi
Zhenya, thanks for the reply!
Actually at this point I see that there're no benefits on using of Akka
Persistence, I could easily use some K/V storage to store the key as the
workflow ID and value - the state of the actors, so upon recovery I could
read from that storage and recreate the FSM
Hello
We're trying to implement something similar (i.e. when Actor recovered, we
want side-effects to not happen again).
During recovery, events are not applied immediately to internal state, but
we're waiting until recovery is completed and then decide what to do next,
based on latest replied
Hi,
It would be very helpful if you give any hint on this.
Thank you
El jueves, 22 de septiembre de 2016, 13:12:59 (UTC-3), Gerard W escribió:
>
> I'm sorry, I did not mention (nor remember :-P) that I was overriding that
> configuration setting to 2552 in my java code.
> So, to make it
Hi,
it took me some time, to find some time. But finally I created a github
project from my solution:
https://github.com/ouven/akka-k8s-seednode
Ruben
Am Dienstag, 19. Juli 2016 02:11:06 UTC+2 schrieb Ashley Aitken:
>
>
> Thanks for sharing Ruben.
>
> I was considering if it could be done
Tal, thanks for the response!
As far as I know, when an actor is recovered through Akka Persistence - the
whole set of events is being re-send to the actor, so it can recover the
state. In my case, some states will have side-effects, like "send an
e-mail" or "update the database". Obviously I
There is the API cluster.joinSeedNodes if you don't want to use config. See
docs for details.
/Patrik
lör 24 sep. 2016 kl. 11:43 skrev :
> If all nodes in cluster is normal node, none is seed.
> How to set one of nodes as seed please?
> I can't do this, no new node can
where to begin with and any powerful libraries for the same?
Which concepts do we need to master for the same apart from the actor
system.
In short, the best approach to build xmpp apis.
Thanks
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>
Hi,
I think you're confusing some things here. Both mapAsync and
mapAsyncUnordered limit the parallelism level in a similar way, the
difference is whether or not they emit the results in the order they were
received.
In other words, mapAsyncUnordered(8) will read 8 messages and start
Hi,
One possible solution using PersistentFSM would be to save the persist with
the timestamp when it happened, and then when applying the event you could
set a timer (using setTimer or system.scheduler) that would trigger the
state change. This way, when the events are processed during
Hi there,
The latest info I have from a prior Akka Team response was that the Akka
Actor Publisher/Subscriber APIs are now deprecated;
and one should be looking at the Graph DSL instead.
i.e. Latest Akka Docs state:
ActorPublisher and ActorSubscriber
cannot be used with remote actors,
Hi Kunal and Johannes,
THANKS for your posts on this -- as I was also wondering how
exception-handling mid-Flow is supposed to work!
Followup questions for you, please:
- Let's say for simplicity that we have only 3 events flowing through a
Streaming Flow with 5 Stages.
- We put a Try block
OK Victor Klang: would you please be so kind as to elaborate with some
helpful details on your prior reply? ;0)
1) My reading of the docs is that the '.buffer' API is necessary to handle
the case where if the Source streams data faster than the Sink can handle
it; then one can run into 'Out
14 matches
Mail list logo