I have been hacking on a discovery plugin for
elasticsearchhttps://github.com/shikhar/eskka using
akka cluster and I wanted to add some automated downing, and the
auto-down-unreachable-after is not really an option since it can lead to
split brain.
So I went with the approach of using a
This is a copy of a post I put up on
Stackoverflowhttp://stackoverflow.com/questions/23403335/akka-pulling-pattern-vs-durable-mailboxes
.
I've been working on a project of mine using Akka to create a real-time
processing system which takes in the Twitter stream (for now) and uses
actors to
Hi Christian,
*To nail down the question: is there a way to extend the settings /
configuration of an already running ActorSystem during runtime?*
No, there is no support for changing the configuration after the system
has been started.
Is there a technical reason for that or simply a
Hi,
I see that you create a router with a set of workers:
// distributing the message processing across a pool of 5 actors
ActorRef workRouter =
akkaSystem.actorOf(new
RoundRobinPool(numOfWorkers).props(Props.create(EventProcessor.class)),
workRouter);
Hi Jabbar,
No, you are not missing anything, PubSub is designed for such cases. Just
be careful not to broadcast too much data since it does not scale linearily.
-Endre
On Sat, May 3, 2014 at 1:06 AM, Jabbar Azam aja...@gmail.com wrote:
I've just looked at the documentation. I can use the
Hi Christian,
Do you have a small reproducible test case that exposes the problem? If you
do, please share so we can look into the possible issue.
-Endre
On Sun, May 4, 2014 at 2:07 PM, Nicola Piccinini piccin...@gmail.comwrote:
Yes, http://doc.akka.io/docs/akka/snapshot/scala/persistence.
Hi Eugene,
On Sun, May 4, 2014 at 6:23 PM, Eugene Dzhurinsky jdeve...@gmail.comwrote:
On Sun, May 04, 2014 at 09:46:50AM +0200, Heiko Seeberger wrote:
class MyActor(myParameter: String) extends Actor with FSM { ... }
context.actorOf(Props(new MyActor(myArgument)))
As far as I
On Sun, May 4, 2014 at 6:23 PM, Eugene Dzhurinsky jdeve...@gmail.comwrote:
On Sun, May 04, 2014 at 09:46:50AM +0200, Heiko Seeberger wrote:
class MyActor(myParameter: String) extends Actor with FSM { ... }
context.actorOf(Props(new MyActor(myArgument)))
As far as I understand, this will
2014-05-05 10:14 GMT+02:00 Akka Team akka.offic...@gmail.com:
Hi Christian,
*To nail down the question: is there a way to extend the settings /
configuration of an already running ActorSystem during runtime?*
No, there is no support for changing the configuration after the system
has
Hi all.
I'm trying a hot swap between an active processor and a backup one, in line
with the
thishttps://www.assembla.com/spaces/akka/tickets/3938#/activity/ticket:
ticket,
to avoid delay while swapping huge actors.
I'm thinking about manually sending my commands to two different actors in
Of course, but if the channel-internal ACK has already arrived, why should
we require another application-level one that might get lost?
Heiko
On Mon, May 5, 2014 at 4:25 PM, Martin Krasser krass...@googlemail.comwrote:
On 05.05.14 14:59, Heiko Seeberger wrote:
On the other hand, an
In the new Router documentation for version 2.3.2
(http://doc.akka.io/docs/akka/2.3.2/java/routing.html), I noticed that in
their very first example, they use a new Router class. From the example, it
seems like they use the Router as a group-router since they first create
Worker actors as
On Mon, May 5, 2014 at 3:13 AM, massivedynamic lu4...@gmail.com wrote:
Anyways, just wanted to get your guys' and gals' thoughts on this. Does
this seem like a viable alternative to doing pulling?
Definitely not my area of expertise -- I haven't gotten a system under
sufficient load yet to
Howdy All,
This is my first post and I am new to Akka and Scala but very excited about
using Akka Persistence and CQRS / ES for a new Web application I am
developing. I have been reading a lot about CQRS / ES and playing around
with Akka Persistence and have a few questions I hope you can
I was considering almost the same thing, but talked myself out of it after
reading this: (
http://www.rabbitmq.com/blog/2012/04/25/rabbitmq-performance-measurements-part-2/see
section Large Queues). RabbitMQ queues messages in memory, regardless
of whether they are durable. The
that what I just want.
I am still wondering should there be an deliveryConfirmedListener just
as redeliverFailureListener.by this way,I will make my life easier.
I don't think the application-level replay should be a answer for that
replay could be lost and there have one internal ACK in the
Hi Matthew,
On 05.05.14 21:21, Matthew Howard wrote:
Has anyone implemented an akka persistence journal for older versions
of Cassandra? I see the current journal is dependent on C* v2.0.3 or
higher (https://github.com/krasserm/akka-persistence-cassandra) but my
app is currently on 1.1.9 and
On 06.05.14 04:26, Vaughn Vernon wrote:
When I override preStart in any way other than invoking
super.preStart() my actor is unable to receive any kind of message. It
seems to be stashing messages, but never delivering them. The only way
I can work around this is by leaving preStart as
18 matches
Mail list logo
