Thank you.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subsc
number of messages in flight for you. It
> might work for bursts of traffic, but if you continuously send more messages
> than the destination can handle you will eventually overflow.
>
> B/
>
> On 15 May 2014 at 07:05:20, 王东 Dong Wang (don...@gmail.com) wrote:
>
&g
annel destination remote or local? Do you see any remoting issues?
>
> B/
>
> On 13 May 2014 at 17:23:25, Dong Wang (don...@gmail.com) wrote:
>
>> I se the interval to 10 seconds. Does my suggestion make any sense to you?
>>
>> 在 2014年5月13日，下午7:11，Björn Antonsso
you have a lot of
> redeliveries happening, then maybe your redeliver interval is set too tight,
> or you are simply overloading your system.
>
> B/
>
>> On 12 May 2014 at 13:56:49, dong (don...@gmail.com) wrote:
>>
>> I'm seeing in my application a lot of chan
I'm seeing in my application a lot of channels message redelivery when the
overall load of the system is high.
Is it a good idea to re-deliver channel message this way:
1. record the latest confirmed time [ of any message]
2. re-deliver the message only iff (current_timestamp -
latest_
I'm seeing in my app a lot of message redelivery by channels when the
overall load of the system is high.
Is it a good idea to re-deliver channel message this way:
1. record the latest confirmed time
2. resend the message : iff (message_delivery_timestamp -
latest_confirmed_timestamp)
According
to http://www.scala-lang.org/docu/files/collections-api/collections_40.html,
immutable HashMap and HashSet takes constant time for adding/removing an
element.
Thanks Martin.
On Thursday, February 20, 2014 6:35:12 PM UTC+8, dong wrote:
>
> For complex processors, I double
;
> On 20.02.14 11:24, dong wrote:
> > I haven't tried making snapshot yet, but I brain mimic the snapshot
> > process and it seems there might be one problem there: what if a
> > processor's memory state is so huge that it takes minutes to write to
> > and read
I haven't tried making snapshot yet, but I brain mimic the snapshot process
and it seems there might be one problem there: what if a processor's memory
state is so huge that it takes minutes to write to and read from disk?
During the snapshot period some services might not be available. It will
r recovery)?
On Thursday, February 20, 2014 4:40:05 PM UTC+8, rkuhn wrote:
>
>
> 20 feb 2014 kl. 09:07 skrev dong >:
>
> And here is another question regarding channel and command sourcing
> Processor.
>
> My understanding is this, when a event is received by Processor:
&
Eventsourced processors
must be commands as opposite to (events + commands). Anyway this just seem
not very convenient for me :)
On Thursday, February 20, 2014 4:03:29 PM UTC+8, rkuhn wrote:
>
>
> 20 feb 2014 kl. 08:47 skrev dong >:
>
> Patrik, I think that's doable workaround. J
And here is another question regarding channel and command sourcing
Processor.
My understanding is this, when a event is received by Processor:
1) persist the event
2) handle the event
3) call event.confirm()
In case something wrong in step 2, channel will attempt to redeliver the
same message
32:34 PM UTC+8, Patrik Nordwall wrote:
>
>
>
>
> On Thu, Feb 20, 2014 at 8:03 AM, Martin Krasser
>
> > wrote:
>
>>
>> On 20.02.14 07:25, dong wrote:
>>
>> Martin, thank you for the quick reply. Great work on AKKA persistence,
>>
>
Martin, let me figure out a empale to make my point.
Suppose my app is a trading platform, it has two memory based models -
account balances (M1), and pending orders (M2). The
deposit/withdraw/createOrder commands shall be handled by M1, lets say
after processing a 'crateOrder' event, it reduc
channel forward Deliver(Persistent(payload1), actor_2_ref)
Why cannot we simple drop "Persistent" so we have:
channel forward Deliver(payload1, actor_2_ref)
Sorry if these questions are silly or don't make sense.
On Thursday, February 20, 2014 1:54:25 PM UTC+8, Martin Krasser wrote:
I'm been playing with the new Akka persistence module, and have the
following questions that I hope to get answered.
1. The document says "If a processor emits more than one outbound
message per inbound Persistent message it *must* use a separate channel
for each outbound message to e
16 matches
Mail list logo
