Hi Patrik,
I tried this with some limited success. Sent messages to the command nodes
(which I only had one up) and they seemed to work and go there and not
query - I only tried a manual test of a few commands, so it is not a true
test.
However, when I tried an ask to the query roles, I got
On Tue, May 5, 2015 at 12:41 PM, Chanan Braunstein
chanan.braunst...@pearson.com wrote:
Hi Patrik,
No I haven't tried that approach yet. Will ClusterSharding know which
nodes have the Persistent actors on them and which the views. I assumed
that I need to tell ClusterSharding which nodes
On Mon, May 4, 2015 at 1:01 PM, Chanan Braunstein
chanan.braunst...@pearson.com wrote:
Sorry, I didn't explain it correctly. I have 3 roles not two.
Frontend
Command (Backend insert of data with Persistent Actors)
Query (Backend query with views)
I guessed so.
So, for now, sounds
Hi Patrik,
No I haven't tried that approach yet. Will ClusterSharding know which nodes
have the Persistent actors on them and which the views. I assumed that I
need to tell ClusterSharding which nodes have what. But, I can try it and
see how goes.
On a similar matter, any chance you can tell
On Fri, May 1, 2015 at 1:19 PM, Chanan Braunstein
chanan.braunst...@pearson.com wrote:
Hi Patrik,
What/where is the limited support for roles in 2.3, do you mean the config
option: akka.contrib.cluster.sharding.role ?
If so, that would only work for one role type, right?
It is reading
Sorry, I didn't explain it correctly. I have 3 roles not two.
Frontend
Command (Backend insert of data with Persistent Actors)
Query (Backend query with views)
So, for now, sounds like my strategy of having three ActorSystems on the
front end (Application, Command, Query) is the way to go till
Hi Patrik,
What/where is the limited support for roles in 2.3, do you mean the config
option: akka.contrib.cluster.sharding.role ?
If so, that would only work for one role type, right?
What I did for now till 2.4 comes out, please let me know if this is not a
good idea, is create two
Hello there,
This new feature will be part of the 2.4.x release which we'll soon start
working on to get over through the finish-line - no hard timeline for it
but soon :-)
If you need it back-ported to 2.3.x we can do this for our customers - in
general new features are not added to maintanance
Thanks Konrad, I will wait till 2.4.
However, thinking about this a bit more adding cluster roles only solves
half the problem. The other issue is that I need to have the actor class on
the local machine to get a ClusterShard. What I would like to do is to
implement CQRS/ES like this:
Play
On Wed, Apr 29, 2015 at 3:08 PM, Chanan Braunstein
chanan.braunst...@pearson.com wrote:
Thanks Konrad, I will wait till 2.4.
However, thinking about this a bit more adding cluster roles only solves
half the problem. The other issue is that I need to have the actor class on
the local machine
Hi Eduardo,
The ClusterSharding extension supports configuration of one role to use a
subset of nodes, but that is not what you are looking for. Instead of using
the ClusterSharding extension you may start the actors yourself and thereby
specify the roles.
See:
ShardCoordinatorSupervisor.props
Many Thanks Patrik.
I'm afraid that if I manage the actors directly I'll lose all the cluster
benefits, include spreading out the mapping objectId - physical node. I
think that I can reduce the problem to a case where I could avoid the
creation of new actors in a particular node in the cluster
On Mon, Jun 2, 2014 at 1:10 PM, Eduardo Fernandes edu...@gmail.com wrote:
Many Thanks Patrik.
I'm afraid that if I manage the actors directly I'll lose all the cluster
benefits, include spreading out the mapping objectId - physical node.
That would not change. The ClusterSharding extension
Many Thanks Patrik for your time!
I'll check the addresses and let you know. With this info I could,
theoretically, implements a smooth node shutdown.
Best regards!
On Mon, Jun 2, 2014 at 3:12 PM, Patrik Nordwall patrik.nordw...@gmail.com
wrote:
On Mon, Jun 2, 2014 at 1:10 PM, Eduardo
It worked perfectly!
Many thanks for your help!
Regards.
El lunes, 2 de junio de 2014 15:24:58 UTC+2, Eduardo Fernandes escribió:
Many Thanks Patrik for your time!
I'll check the addresses and let you know. With this info I could,
theoretically, implements a smooth node shutdown.
15 matches
Mail list logo
