What version of Akka are you using? How do you create the CHR?
/Patrik
On Wed, Mar 19, 2014 at 10:35 PM, Sendhil Kumar M sendhi...@gmail.comwrote:
I have implemented two CHR where one Router has 20 routees of Actor B and
another CHR router with 5 routees and both these Routers uses the Same
Yes. Can you please tell me how to do that for messages in ReliableProxy? I
would like to make contribution.
Thanks for help.
On Tuesday, 18 March 2014 17:17:26 UTC+8, Patrik Nordwall wrote:
Hi,
That is because the original message is wrapped in a
ReliableProxy.Message, which only has
It seems my message was deleted. So sorry post again.
Can you please give me advice on how to serialize message in ReliableProxy?
I would like to make contribution.
Apology if sending redundant messages.
Thanks
On Tuesday, 18 March 2014 17:17:26 UTC+8, Patrik Nordwall wrote:
Hi,
That
20 mar 2014 kl. 08:53 skrev lee json jsonlee...@gmail.com:
It seems my message was deleted. So sorry post again.
We don’t delete messages, but this list is moderated to keep the spam out; I
added a welcome message explaining this yesterday.
Regards,
Roland
Can you please give me advice
The recording is here: https://www.youtube.com/watch?v=r5lecCBazvE
and the slides: http://www.slideshare.net/patriknw/akka-persistence-webinar
/Patrik
On Thu, Mar 20, 2014 at 12:41 AM, James james.le...@gmail.com wrote:
I missed the live, is this going to be available on Yotube?
--
Read
Hi Allan,
Take a look at this Typesafe Activator template:
https://typesafe.com/activator/template/akka-sample-multi-node-scala
Let us know if that solves your problem or not.
/Patrik
On Wed, Mar 19, 2014 at 10:55 PM, Allan Brighton allane...@gmail.comwrote:
Correction: The
On Thu, Mar 20, 2014 at 8:46 AM, lee json jsonlee...@gmail.com wrote:
Yes. Can you please tell me how to do that for messages in ReliableProxy?
I would like to make contribution.
Great.
1. Create a protobuf representation of ReliableProxy.Message,
see Send in
Hi !
We use Akka 2.3.0. with the default configuration for akka remote
We have 2 system on 2 nodes running which are remote connected and watch
each other.
When we put e.g. one Node-A under heavy heavy load the system gets
quarantined by Node-B with the following log.
*09:46:51.475 WARN
I think I may have found a bug:
Please find my code in this gist https://gist.github.com/dong77/9659988
If you delete line75, the replay will work, otherwise, each replay will
genera new events.
Here is the failure senario:
There are two processors A and B. A handles persistent messages of
Hi Robin,
Thanks for sharing. The Akka core team doesn't have the bandwidth to review
this.
Regards,
Patrik
On Tue, Mar 18, 2014 at 9:21 AM, Robin Bakkerus robin.bakke...@gmail.comwrote:
Hi
After participating in the Scala reactive course at Coursera last year, I
jumped on the Scala, Slick,
El jueves, 20 de marzo de 2014 09:44:28 UTC+1, Patrik Nordwall escribió:
Hi Eduardo,
Many thanks for your time, Patrik.
On Thu, Mar 20, 2014 at 12:04 AM, Eduardo Fernandes
edu...@gmail.comjavascript:
wrote:
Hi all.
We have a system where we've implemented a pipeline strategy as
Hi Patrik,
It turns out that this line was the problem:
unmanagedSourceDirectories in Test += baseDirectory { _ / src /
multi-jvm / scala },
I added it to fix a problem in the generated Idea-13.1 projects, which are
always missing the multi-jvm source directory in the settings.
For some
I am using Scala 2.9.2 and Akka 2.0.x. I have two actors:
class DoWorkActor extends Actor {
val manager = context.system.ActorSelection(user/manager)
def receive = {
case go = {
// do some work
manager ! success
}
}
}
class ManagerActor extends
On Thu, Mar 20, 2014 at 12:25 PM, Eduardo Fernandes edu...@gmail.comwrote:
El jueves, 20 de marzo de 2014 09:44:28 UTC+1, Patrik Nordwall escribió:
Hi Eduardo,
Many thanks for your time, Patrik.
On Thu, Mar 20, 2014 at 12:04 AM, Eduardo Fernandes edu...@gmail.comwrote:
Hi all.
We
I am using akka 2.3.0 and this is how i am creating the CHR.
So my req is that which ever message went to a routee of TestConnActor they
should all be consolidated as list in the Aggregator actor.
So if message 1 and 2 made it to TestConnActor routee1 and message 3 and 4
made it to
Thank you so much!
On Thursday, March 20, 2014 7:41:34 AM UTC+8, James wrote:
I missed the live, is this going to be available on Yotube?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Hi Roger,
On Mon, Mar 17, 2014 at 2:34 PM, Roger Alsing rogerals...@gmail.com wrote:
This is related to my first question regarding remote deployment protobuf
message.
The DaemonMsgCreateData has a PropsData, which in turn holds a list of
args that is needed in order to create the actor
I ended up changing my DoWorkActor like this:
class DoWorkActor(managerRef: Option[ActorRef] = None) extends Actor {
lazy val managerSel = context.system.actorSelection(user/manager)
def receive = {
case go = {
// do some work
tellManager(success)
That looks better. Consider if it be possible to always pass in
the managerRef:
ActorRef instead of using actorSelection.
By the way, the actorSelection should probably be /user/manager
I would use TestActorRef only in very special cases. In fact, I have not
found a reason to use it one single
I corrected the deprecated version. Thanks for your help. But still i see
the same behavior.
So yes i have three Routers set up with 3 different routee sets and my
objective to route all the messages with same hashKey to single instance of
TestAdaptorActor.
So i was trying to build a list
Sounds like you don't want consistent hashing:
http://en.wikipedia.org/wiki/Consistent_hashing
On Thu, Mar 20, 2014 at 4:09 PM, Sendhil Kumar M sendhi...@gmail.comwrote:
I read the article on ConsistentHashingGroup but is it possible for me to
have different types of routees(Actors) in the
Thanks for your suggestion. So if i have two different actors with CHR and
there is no guarantee that the messages will be routed to same routee
within the CHR's. If thats the case then i got to change my approach.
Consistent hasing routing will work only for the same type of actors is it?
On Thu, Mar 20, 2014 at 4:22 PM, Sendhil Kumar M sendhi...@gmail.comwrote:
Thanks for your suggestion. So if i have two different actors with CHR and
there is no guarantee that the messages will be routed to same routee
within the CHR's. If thats the case then i got to change my approach.
I'm looking at using the Pull Pattern (such as described at
http://letitcrash.com/post/29044669086/balancing-workload-across-nodes-with-akka-2),
with workers explicitly requesting work from a master. While the master
handles worker failures by rescheduling jobs, I'm wondering what are
Many thanks Patrik for the info!!
I'll check the links you mentioned. I think you're right, the frameworks
could improve a lot our performance.
Best regards!!
El jueves, 20 de marzo de 2014 13:13:28 UTC+1, Patrik Nordwall escribió:
On Thu, Mar 20, 2014 at 12:25 PM, Eduardo Fernandes
On Thu, Mar 20, 2014 at 7:49 PM, √iktor Ҡlang viktor.kl...@gmail.comwrote:
Yeah, using Death Watch is appropriate. One solution: if you use Akka
Cluster then it is easy to find the next master deterministially by just
scanning the membership list in order and using the first node that has an
26 matches
Mail list logo
