> 27 maj 2014 kl. 04:43 skrev Eugene Dzhurinsky :
>
> It seems that I've fixed this weird behavior by making messages, being sent
> to the cluster, implementing the ConsistentHashable trait
>
> At least, the sample project and the components from my prototype - are both
> working well now.
>
Awesome, subscribed :)
Thanks,
Adam
On Monday, May 26, 2014 3:04:30 PM UTC+2, Konrad Malawski wrote:
>
> Hey Adam,
> Patrik has right now opened a ticket and started exposing the
> ActorProducer abstraction :-)
> https://github.com/akka/akka/issues/15288 This will help a lot in
> implementing e
>
>
> - another thing is if the streams are thought to be more local, or remote
>> as well? There's currently the TCP stream implementation, which I guess
>> would indicate remote as well (and in such scenarios the need for
>> backpressure arises quite naturally, maybe even more than in locally
It *seems* that I've fixed this weird behavior by making messages, being
sent to the cluster, implementing the *ConsistentHashable* trait
At least, the sample project and the components from my prototype - are
both working well now.
So it turns out that for the case if there are several *nested
Hi Patrik,
This makes sense. I am using event sourcing in some places to ensure that some
action is performed (channels will be removed/changed right). In preStart I
send a message to self to restart processing. The actor rebuilds its state
after which it will receive the restart processing mes
Hi,
The docs also advice against auto-downing. However I do not really get the
alternative. Manual downing would be unworkable, because it could render your
application unavailable for to long. So should I implement some strategy in my
akka solution, or in some external monitoring system?
How
Hello Anil,
The size of the cluster does not really influence this, but downing it's
members and partitions do.
In theory this problem can appear always when there is a "split brain"
partition, meaning: when 2 clusters are formed - this is what happens in
the above example.
It would also happen if
On Mon, May 26, 2014 at 07:41:53AM +0200, Patrik Nordwall wrote:
> Hi Eugene,
>
> I have not looked at the code yet, but in the config you have two
> consistent hashing routers. The envelope is unwrapped when the message pass
> the first consistent hashing envelope. Could that be the reason?
Well
Hey Adam,
Patrik has right now opened a ticket and started exposing the ActorProducer
abstraction :-)
https://github.com/akka/akka/issues/15288 This will help a lot in
implementing external producers. :-)
On Mon, May 26, 2014 at 2:52 PM, Endre Varga wrote:
> Hi Adam
>
>
>> - is it reasonable (th
Hi Adam
> - is it reasonable (thinking about reactive streams in general) to have an
> actor which produces elements on-demand (instead of providing a
> collection/iterator/() => as is currently supported)? As far as I
> understand the current implementation, subscribers explicitly ask
> publishe
On Monday, May 26, 2014 2:25:52 PM UTC+2, Konrad Malawski wrote:
>
> One thing unanswered from the previous email:
>
> Is it in the "spirit" of akka-stream/reactive streams to implement your
> own producers? Or should all producers (publishers) be created by the
> framework?
>
> In theory react
One thing unanswered from the previous email:
Is it in the "spirit" of akka-stream/reactive streams to implement your own
producers? Or should all producers (publishers) be created by the framework?
In theory reactive streams aim to be usable between frameworks - so an Rx
Producer would be consum
12 matches
Mail list logo
