Hello,
Im new to Akka/Akka Persistence.. Though the documentation seem to provide
information on the Akka View -- Im looking for use cases of the same. Is it
for supporting High Availability -- wherein if the Processor is running on
one node and Akka View can be on another node and provide HA
Hello Syed,
yes / no.
yes - it's possible to spin up a View for the same processorId on a
different node in the cluster. It can be used as a read-model.
no - it can not change into becoming a processor if the main processor
goes down. A view is a view.
The View's use-case is to be able to have a
Hi Björn,
today I found out that the root cause seems to be the length of the fully
qualified class name of the snapshot class. If the length (pacakge+class
name) exceeds 60 characters an EOFException is thrown instead of calling
fromBinary.
Here's my reference.conf:
akka {
actor {
Can anyone point in the right direction with this one, probably something
obvious I'm missing!
I'm trying to debug a strange Cluster issue…
I have 3 actor systems in a cluster (all in the same JVM) communicating via
the distributed bus. (It's just a test app at the moment, and in production
On Wed, 2014-05-21 at 11:02 -0700, Alanlit wrote:
On Wednesday, May 21, 2014 8:43:56 AM UTC-7, Patrik Nordwall wrote:
Verify that you have protobuf version 2.5.0 in your classpath.
/Patrik
Good call !! I found that a third party library has (of course) an
old version of
Hello James,
could you first try the latest Akka which is 2.3.3?
There has been multiple issues fixed in three maintenance releases since
Akka 2.3.0.
On Thu, May 22, 2014 at 4:42 PM, James Bunch james.x.bu...@gmail.comwrote:
Can anyone point in the right direction with this one, probably
I meant to say that ClusterClient is only one way. You can use
Send/SendToAll/Publish
to talk to the cluster from the outside. However ClusterClient is not
suitable when trying to talk to outside from within the cluster.
On Wed, May 21, 2014 at 5:56 PM, Luis Medina lu4...@gmail.com wrote:
Thx to both! -- This was helpful!
-Syed
On Thursday, May 22, 2014 3:03:57 AM UTC-7, Patrik Nordwall wrote:
What you are looking for has previously been tracked as
https://github.com/akka/akka/issues/13938
/Patrik
On Thu, May 22, 2014 at 10:26 AM, Konrad Malawski
Hi Luis,
On Thu, May 22, 2014 at 9:19 PM, Luis Medina lu4...@gmail.com wrote:
Hi Martynas,
Thank you so much for answering my questions. I know it was quite a
lengthy read. Just got a few follow-up comments/question:
I think I understand sharding now. In doing something like:
Hi Patrik,
You are absolutely correct. I don't know what was going through my mind
when I said that there are multiple instances of an entry running. Haven't
been getting much sleep lately :/
As for my use-case, I'm trying to build a pipeline that takes in a data
stream and processes it in
I'd love to hear the answer to this too!
I've solved the problem by injecting actorRefs but it does seem to lose the
point of actor supervision.
The other technique I've tried in one spot is to use the TestActorRef to
get the underlyingActor and then set the actorRef on that. This means that
Well, in my case, I'm creating TestProbes and passing them into the actor
under test so that I can verify what it does with them.
For example, I have one class which communicates with 3 other actors and I
mock out all of them with TestProbes.
However, it does feel like a lot of work which is a
12 matches
Mail list logo
