[akka-user] Re: Questions about Kafka Consumer of Transient messages via Akka-Streams on Multiple Nodes

.to(Sink.actorRef(getSelf(), NotUsed.getInstance())) .run(ActorMaterializer.create(getContext())); } On Wednesday, December 6, 2017 at 11:06:26 AM UTC-6, kraythe wrote: > > We are using Kafka to store messages that are produced by a node in our > cluster and t

[akka-user] Questions about Kafka Consumer of Transient messages via Akka-Streams on Multiple Nodes

We are using Kafka to store messages that are produced by a node in our cluster and to be distributed to all nodes in the cluster and I have it mostly working with akka-streams but there is a couple of questions I have to tie this up. There are some constraints to this. First of all the

[akka-user] Re: PhiAccrualFailureDetector Constantly Spamming logs but nodes seem unaffected.

e message we are sending are pretty small. > > I would have to dig to see if I can find when exactly these started > occurring, but if I have to guess, I would say this started happening when > we moved from Akka 2.4 tot 2.5. > > Lukas > > On Thursday, 30 November 2017 15:31:

Re: [akka-user] Distributing lots of large messages to a cluster on startup issue.

: > > Maybe a shared cache would be a better way to deal with it? > > On Thursday, November 30, 2017 at 12:41:28 PM UTC-5, kraythe wrote: >> >> Yeah the problem is it cant be broken up, its sort of all or nothing. I >> cant be too specific beyond it being a parametric matrix.

Re: [akka-user] Distributing lots of large messages to a cluster on startup issue.

, December 1, 2017 at 1:53:52 AM UTC-6, Patrik Nordwall wrote: > > > > On Fri, Dec 1, 2017 at 8:03 AM, kraythe <kra...@gmail.com > > wrote: > >> What about using something like Kafka to distribute the matrix? >> > > Sounds like overkill (a lot of infra) if tha

Re: [akka-user] Distributing lots of large messages to a cluster on startup issue.

gt; this server around. That server can offer the last ten versions (or >> whatever), could use the hash of the preserialized map as identifier. That >> way you can explicitly manage the dissemination and its resource usage. >> >> Regards, >> >> Roland >>

Re: [akka-user] Distributing lots of large messages to a cluster on startup issue.

shed again. Otherwise you could use DistributedData to > share them. > > /Patrik > tors 30 nov. 2017 kl. 14:35 skrev kraythe <kra...@gmail.com > >: > >> Greetings, >> >> We have an actor structure where there is a cluster sharded actor that >> cal

Re: [akka-user] Distributing lots of large messages to a cluster on startup issue.

tedData to > share them. > > /Patrik > tors 30 nov. 2017 kl. 14:35 skrev kraythe <kra...@gmail.com > >: > >> Greetings, >> >> We have an actor structure where there is a cluster sharded actor that >> calculates a parametric matrix of about 7 meg and

[akka-user] PhiAccrualFailureDetector Constantly Spamming logs but nodes seem unaffected.

We are constantly getting messages like this in our logs. 2017-11-30 14:28:31,181 [WARN ] [PhiAccrualFailureDetector] (akka.remote.PhiAccrualFailureDetector@808f8ad) - heartbeat interval is growing too large: 1766 millis I understand the theory behind this for early detection of node failure

[akka-user] Distributing lots of large messages to a cluster on startup issue.

Greetings, We have an actor structure where there is a cluster sharded actor that calculates a parametric matrix of about 7 meg and has to distribute it to 5 other nodes for consumption. First of all there are the following constraints. 1. The matrix has to be generated in one place. 2. The

[akka-user] Re: Problem of routing different java objects with same id to same actor

You could implement your own router actor and protocol for routing messages but why bother. Cluster sharding has already done that for you. Look into that. On Wednesday, August 30, 2017 at 4:47:44 AM UTC-5, Wei Guo (SH-LTS) wrote: > > Hi everyone, > > I'm a newbie for Akka, for load balance

Re: [akka-user] Akka-HTTP creating a directive to create a unique request id?

gleSlash { > comlete(requestId.toString) > } > } > > Is that what you're looking for? See > http://doc.akka.io/docs/akka-http/10.0.9/scala/http/routing-dsl/directives/custom-directives.html#directives-from-scratch > > for more details. > > > Kind regards, >

Re: [akka-user] Akka-HTTP creating a directive to create a unique request id?

gt; > > Kind regards, > > Arnout > > On Thu, Aug 24, 2017 at 1:55 AM, kraythe <kra...@gmail.com > > wrote: > >> Greetings, >> >> I am currently using the low level API but lookign again at the DSL. I >> have been trying to figure out i

[akka-user] Akka-HTTP creating a directive to create a unique request id?

Greetings, I am currently using the low level API but lookign again at the DSL. I have been trying to figure out if there is a way to create a directive that creates a unique request UUID and allows other directives to access that UUID in every sub directive. Basically I want something like

[akka-user] How to custom handle endpoints in Akka-HTTP DSL?

Ive been using the low level API but taking another look at the DSL . I have a number of actors that all base on a class called EndpointActor and have some basic facilities to handle errors, problems in auth and so on in custom ways. I want to know if this is possible in the DSL. The base

[akka-user] Upgrade to 2.5.3 Cluster Nodes can't Connect.

I am trying to upgrade our system to 2.5.3 and play 2.6 and when we do so the cluster nodes can no longer connect to each other. We get logs like this: Jul 07 16:25:38 jp-6.mycompany.com application-9001.log: 2017-07-07 21:25:38 + - [WARN] - [ReliableDeliverySupervisor]

[akka-user] Re: Has akka-http has abandoned per request actors in favor an anti-pattern DSL?

Sorry, I have been buried with work. The problem with the DSL approach in my opinion is that it leaves too much space for error and strange things happening and at the same time it hamstrings you into a particular flow that may or may not be appropriate to the problem. Just to have some fun,

Re: [akka-user] Re: Has akka-http has abandoned per request actors in favor an anti-pattern DSL?

It sends the final result back to its "requestor" and stops itself. > > With Spray I didn't need the outermost ask(), but I think it's fine having > one at the outermost layer. > > On Fri, Apr 7, 2017 at 9:45 PM, kraythe <kra...@gmail.com > > wrote: > &g

[akka-user] Re: Has akka-http has abandoned per request actors in favor an anti-pattern DSL?

Stoner wrote: > > Hi Kraythe, > > Perhaps it helps to see a real world example that we've been working on - > with a good number of routes involved. > > This is from our AkkaHttpServer class. It's job is to inject all the > routes (ordersV2, searchv3, searchTerms, pe

[akka-user] Re: question on Akka concurrency and ForkJoinPool

In akka, the dispatcher manages the threads for you. Most akka systems ignore the existence of the thread pool entirely except when a third party library requires an execution context or something and even then the best practice is to just reference the dispatcher. That aside, since the

Re: [akka-user] Re: Has akka-http has abandoned per request actors in favor an anti-pattern DSL?

kka.io/docs/akka-http/current/scala/http/routing-dsl/index.html#longer-example >> >> It has examples of how to delegate an endpoint's business logic off to >> actors or futures. >> >> >> On Sunday, April 2, 2017 at 7:09:32 PM UTC-6, kraythe wrote: >>>

[akka-user] Re: Has akka-http has abandoned per request actors in favor an anti-pattern DSL?

longer example of the DSL? > > > http://doc.akka.io/docs/akka-http/current/scala/http/routing-dsl/index.html#longer-example > > It has examples of how to delegate an endpoint's business logic off to > actors or futures. > > On Sunday, April 2, 2017 at 7:09:32 PM UTC-6, kraythe wrote

[akka-user] Re: Has akka-http has abandoned per request actors in favor an anti-pattern DSL?

nger example of the DSL? > > > http://doc.akka.io/docs/akka-http/current/scala/http/routing-dsl/index.html#longer-example > > It has examples of how to delegate an endpoint's business logic off to > actors or futures. > > On Sunday, April 2, 2017 at 7:09:32 PM UTC-6, krayt

[akka-user] Has akka-http has abandoned per request actors in favor an anti-pattern DSL?

I was really excited about akka-http as I would be able to unburden my code from the baggage of play and handle my server side as a pure akka actors app but unless I am much mistaken something is dreadfully amiss with the implementation. One of the main core features is the actor paradigm and

[akka-user] Best practice when dealing with exceptions in child actors when the actor cant crash or needs to return error to end user?

There are two situations where i need to deal with exceptions outside of the normal "Let it crash" paradigm. First is an actor that can't crash. I have some actors that cache a ton of information and their startup can take quite a while. If some method throws in the actor unless the exception

[akka-user] Catching exceptions in actor receive?

I have an actor that I would like to not fail. However there is a possibility that a user might call the actor with some problem that results in an exception not being thrown. The proscribed way to handle this is to fial the actor and have the supervisor restart the actor, however that is not

[akka-user] [Akka-HTTP] (Java) Per Request Actors Possibility and Best Practices?

I am currently using playframework for my Http stuff and want to go to Akka-HTTP for the new project. However from my reading and playing with Akka-Http it seems that I have to stuff a ton of logic into the routes and I don't like that. Consider the following from the docs: public class

[akka-user] akka.remote.transport.ProtocolStateActor/invoke is reporting as SLOW on NewRelic

On our NewRelic dashboard this is the output: >From the point of view this invocation is extremely slow. I am not sure if

[akka-user] [Cluster Sharding] Futures timed out after [20000 milliseconds] when starting?

When starting our server in a cluster of 9 nodes we are getting this error randomly. This causes our actors that use cluster sharding to restart and basically fubars the server. Any idea what might be causing this? Thanks in advance. 2017-02-16 17:20:12 + - [ERROR] -

[akka-user] Node Roll Error with Distributed Data.

Greetings, After having some issues with akka persistence when rolling nodes. Since we only use persistence for the cluster sharding coordinator, I decided to try out the Distributed Data module and I am getting the following error on all my cluster sharded actors. This happens right before

Re: [akka-user] Problems with Persistence when rolling nodes.

ve() or .down() to down nodes, > then balancing happens. > > -- > Konrad `ktoso` Malawski > Akka <http://akka.io> @ Lightbend <http://lightbend.com> > > On 18 November 2016 at 18:29:07, kraythe (kra...@gmail.com ) > wrote: > > Roland, > > I am wondering

Re: [akka-user] Problems with Persistence when rolling nodes.

with the quoted > persistenceId active at the same time. > > Regards, > > Roland > > 18 nov. 2016 kl. 17:49 skrev kraythe <kra...@gmail.com >: > > Greetings, I am currently using the community plugin for mysql > ("com.github.mauricio" > %% "mysql-async&quo

[akka-user] Problems with Persistence when rolling nodes.

Greetings, I am currently using the community plugin for mysql ("com.github.mauricio" %% "mysql-async" % "0.2.16") for AKKA persistence. However, when I perform a rolling restart I get exceptions like the following: Nov 18 10:11:20 vtest-app01 application-9001.log: 2016-11-18 16:11:19 >

[akka-user] Graceful node shutdown. Is there a batter way?

Greetings, I have a node with a number of top level actors and cluster shards that I want to shut down gracefully. I have added the redacted code before for the startup and shutdown via a SystemManagerActor but I am staring at it wondering if there is a better way. A number of questions occur.

Re: [akka-user] Problem with nodes going down and ClusterSharding

owning strategy are you using? We recommend against auto-down. > We recommend Split Brain Resolver or similar. No downing strategy at all is > not an option. Then you must down manually (by human operator). > > /Patrik > lör 12 nov. 2016 kl. 18:22 skrev kraythe <kra...@gmail.com >

Re: [akka-user] Problem with nodes going down and ClusterSharding

; What other downing strategy are you using? We recommend against auto-down. > We recommend Split Brain Resolver or similar. No downing strategy at all is > not an option. Then you must down manually (by human operator). > > /Patrik > lör 12 nov. 2016 kl. 18:22 skrev kray

[akka-user] Problem with nodes going down and ClusterSharding

Greetings, We have a cluster shared actor that manages the UserSession for our users. The actor's persistence id is the name of the session id and its shard is determined by sessionId.hashCode() % 37. All of this works beautifully except when a node goes down either crashing (simulated with

[akka-user] Re: [Akka 2.4.7] + [Play 2.5] Inject Serialization Bindings Config Programmatically??

t;, > I'm not at home so can't look the exact key nor copy & paste my config > section for that. > That way any object that implements serializable will be serialize with > Kryo, objects that don't implement Serializable you will have bind > explicitly. > > HTH, > &g

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

All I do is issue a Cluster.get(system).leave(cluster.selfAddress) On Monday, September 12, 2016 at 9:49:22 AM UTC-5, √ wrote: > > What are you using/doing for downing? > > On Mon, Sep 12, 2016 at 4:13 PM, kraythe <kra...@gmail.com > > wrote: > >> No, we have d

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

No, According to suggestions in the docs, I am not running auto-downing. Should I change that policy ? On Sunday, September 11, 2016 at 3:22:22 PM UTC-5, √ wrote: > > Are you running auto-downing? > > On Sat, Sep 10, 2016 at 11:43 PM, kraythe <kra...@gmail.com > &g

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

No, we have disabled that as per suggestion in the docs. Should we? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives:

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

1.0.x/Install#EC2-Installation >> >> * ConductR and SBR are Lightbend products >> >> -- >> Cheers, >> √ >> >> On Sep 10, 2016 6:46 PM, "kraythe" <kra...@gmail.com > >> wrote: >> >>> I am not following you on this one.

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

Problem is I need to prove the product in production before i can suggest purchase of expensive platforms. :) On Saturday, September 10, 2016 at 11:58:36 AM UTC-5, Justin du coeur wrote: > > On Sat, Sep 10, 2016 at 12:46 PM, kraythe <kra...@gmail.com > > wrote: > >>

Re: [akka-user] Cluster seed nodes resulting in multiple split brains?

the list of >> discovered nodes stabilize, i.e. not changing within X seconds. Then sort >> them to make sure the same is used as the first from all places. Then >> joinSeedNodes with that sorted list. >> >> To be completely safe you must manually decide which one

Re: [akka-user] Configuration of SerializationBindings Programmatically?

They specify the config just like any other serializer, with the serialization bindings. They have no examples of how to do it via code. But I think I can run with this, thanks. On Friday, September 9, 2016 at 4:12:50 PM UTC-5, Justin du coeur wrote: > > On Fri, Sep 9, 2016 at 3:49 PM, k

Re: [akka-user] Configuration of SerializationBindings Programmatically?

: > > parseMap +1 > > -- > Konrad `ktoso` Malawski > Akka <http://akka.io> @ Lightbend <http://lightbend.com> > > On 9 September 2016 at 22:10:33, Viktor Klang (viktor...@gmail.com > ) wrote: > > ConfigFactory.parseMap? > > -- > Cheers, > √ >

Re: [akka-user] Configuration of SerializationBindings Programmatically?

]: > https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/actor/ActorSystem.scala#L141 > > On Fri, Sep 9, 2016 at 9:49 PM, kraythe <kra...@gmail.com > > wrote: > >> I am using Akka-kryo by Roman Levenshtein >> <https://github.com/romix/akka-kryo

Re: [akka-user] Configuration of SerializationBindings Programmatically?

lex, and the process of figuring out how it works > teaches pretty much everything critical about using Kryo with Akka... > > On Fri, Sep 9, 2016 at 3:29 PM, kraythe <kra...@gmail.com > > wrote: > >> Greetings, >> >> In reference to the configuration of ser

[akka-user] Configuration of SerializationBindings Programmatically?

Greetings, In reference to the configuration of serialization bindings I would like to do this programatically instead of using the config file. I have a type with a static map of types and binding ids based on a Kryo plugin to Akka. What I would like to do is create bindings based on that

[akka-user] Cluster seed nodes resulting in multiple split brains?

Greetings, We are having some problems with our cluster configuration that manifest themselves in the following log lines (redacted for confidentiality reasons. Sep 09 00:58:10 host1.mycompany.com application-9001.log: 2016-09-09 05:58: 10 + - [WARN] - [OrdersActor]

[akka-user] Method to block Migration of Cluster Sharded Actors in a Certain State

I have a cluster shared actor that basically has two states; IDLE and BUSY. The actor is cluster shared because I need the behavior of having only a single one of these in the cluster per user and I want all of the messages that the actor to handle to be serialized per user. The actor mostly

Re: [akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

I get the idea. But does that mean I should create a top level actor like the /user guard but under user for all my actors and wait for the member to leave ? This is occurring inside of a Play Framework shutdown, so I would have to figure out how to orchestrate that. On Monday, July 25, 2016

Re: [akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

nd <http://lightbend.com> > > On 25 July 2016 at 20:27:29, kraythe (kra...@gmail.com ) > wrote: > > In our code prior to shutting down a node we issue the following call. > > val cluster: Cluster = Cluster.get(system) > cluster.leave(cluster.selfAddress) > >

[akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

In our code prior to shutting down a node we issue the following call. val cluster: Cluster = Cluster.get(system) cluster.leave(cluster.selfAddress) However, despite that the other node still complains about unreachable node. Any way I can stop this? 2016-07-25 13:23:33 -0500 - [WARN] -

[akka-user] What is ProtocolStateActor.invoke and why is it so time consuming?

We have been doing load tests on our development environment to isolate out slow operations in our system. One of the endpoints that NewRelic reported taking lots of time is ProtocolStateActor.invoke. The output is provided in the attached, redacted for NDA reasons, screenshot. Can anyone tell

Re: [akka-user] Re: Is this a viable paradigm for PerRequest actors on Synchronous system?

Thanks for all the feedback. To be clear you seem to think my second approach is the better of the two ideas and I souls just create a bunch of these in a router? My only concern there is that if a single actor fails requests can queue up in that actors mailbox. When the router restarts the

[akka-user] Re: Is this a viable paradigm for PerRequest actors on Synchronous system?

ven't > figured it out, let me know if you do or don't in a couple of hours. > > HTH, > > Guido. > > On Wednesday, June 29, 2016 at 3:25:23 PM UTC+1, kraythe wrote: >> >> Thanks for the reply Mark. I understand where you are comming from but >> the actual

[akka-user] Re: Is this a viable paradigm for PerRequest actors on Synchronous system?

Thanks for the reply Mark. I understand where you are comming from but the actual implementation in proprietary code is quit a bit more complex. Future a response drives data needed for future b and c requests. The actual code with completable futures is significantly more complex. I would

[akka-user] Is this a viable paradigm for PerRequest actors on Synchronous system?

Greetings, I am trying to glue a play controller together with an Actor System in a large legacy codebase. Reimplementing the whole codebase as a raw actor system is not viable in the short term so it will have to take over piece by piece. What I am wondering is if the following paradigm is

[akka-user] Best way to deal with Actors that integrate other Actor Data?

Lets say I create an actor that will serve JSON to an end user but that actor returning the OverviewJson has to get data from three different actors and wait for them all to return a response before proceeding. Now I could create an actor that uses the ask patter to call all three other actors

[akka-user] Gluing with Synchronous System and abuse of RPC?

I have been introducing actors and Akka into a playFramework application and since I cant re-engineer the whole application, there is a number off times I do code like the following: final CompletableFuture summary = PatternsCS.ask(Manager.actorSelection(MyApp.getActorSystem()),

[akka-user] [Akka 2.4.7] + [Play 2.5] Inject Serialization Bindings Config Programmatically??

Greetings, I have a large map of serialization bindings basically in a big map where type ids are defined that I would like to inject into the config at startup but I have been unable to figure out how to do this. These serialization bindings are used by 4 or 5 pieces of tech we have in the

[akka-user] Re: Runtime issue with Cluster Sharding.

No it was only local. But on my vpn it changes my ip all the time. On Sunday, June 12, 2016 at 6:21:13 PM UTC-5, Ryan Tanner wrote: > > The mention of VPN has me tingling. Are you trying to join to a cluster > across a WAN? > > On Sunday, June 12, 2016 at 12:20:08 PM UTC-6

[akka-user] Re: Runtime issue with Cluster Sharding.

For the next person with this problem, the resolution is that if you even run with one node you have to either configure seed nodes, manually or programmatically join the cluster for the sharding system to work. My error was not specifying the host name exactly in my remoting settings and

[akka-user] Re: Runtime issue with Cluster Sharding.

> > cluster { > // FIXME cant use static seed nodes config! > seed-nodes = [ > *"akka.tcp://application@**w.x.y.z* > *:2551"* "akka.tcp://application@localhost:2551" > ] > > So the first line for the seed nodes works but the second doesn't. The problem is that IPs of our

Re: [akka-user] Re: Runtime issue with Cluster Sharding.

; sön 12 juni 2016 kl. 18:42 skrev kraythe <kra...@gmail.com >: > >> I am wondering if there is some problem since I am running Akka inside of >> play 2.5 as an integrated environment. It would suck if thats a problem for >> cluster config because that means I would h

Re: [akka-user] Subclassing Shard Region Actor a good idea?

ar data structure but mine has a primitive > specialization. > > HTH, > > Guido. > > On Sunday, June 12, 2016 at 5:54:47 PM UTC+1, kraythe wrote: >> >> I don't necessarily want to drop location transparency. I am just >> concerned because I have millions of actors across t

Re: [akka-user] Subclassing Shard Region Actor a good idea?

ght of "location transparency" . As usual your advice is appreciated. On Sunday, June 12, 2016 at 10:32:32 AM UTC-5, Justin du coeur wrote: > > On Sat, Jun 11, 2016 at 2:14 PM, kraythe <kra...@gmail.com > > wrote: > >> It doesnt seem very specific

[akka-user] Re: Runtime issue with Cluster Sharding.

10, 2016 at 2:18:43 PM UTC-5, kraythe wrote: > > Greetings, > > I apologize if this has been asked but I am having what I assume is a > config problem. When I start a single node I get the following logged > errors and my sharded actors don't start. The errors are like such: &g

Re: [akka-user] Re: Runtime issue with Cluster Sharding.

ocal"] } } } On Sunday, June 12, 2016 at 9:57:29 AM UTC-5, Justin du coeur wrote: > > Well, the problem *looks* to me like the cluster isn't joining up at all. > So if you don't do auto join, then you need to set that up > programmatically. (Don't recall

[akka-user] Re: Runtime issue with Cluster Sharding.

What if I dont want any auto join at all. I took out the seed nodes and I get the same problem. On Saturday, June 11, 2016 at 2:24:10 PM UTC-5, Rafał Siwiec wrote: > > akka.remote.netty.tcp.port - instead of 0 you should use 2551. -- >> Read the docs: http://akka.io/docs/

[akka-user] Subclassing Shard Region Actor a good idea?

The use case is I have a bunch of entities that are in an RDBMS and they are represented in memory by an actor per entity and those entities are spread across the cluster using ClusterSharding (assuming I can figure out why it wont start for me). However, on a per-node basis I would like to be

Re: [akka-user] Re: Another Newbie Question -- Sending message to Millions of Cluster sharded actors.

nd this approach unless the situation is dire > enough to warrant it -- it's a lot of work, and requires you to take on a > lot of responsibility for the sharding -- but consider it food for thought > if things look problematic... > > On Fri, Jun 10, 2016 at 2:43 PM, kraythe <

[akka-user] Re: Another Newbie Question -- Sending message to Millions of Cluster sharded actors.

The problem is I need to have the actors running and from what I understand the sharding system doesn't start an actor until you actually pass a message to an actor with that id. They cant subscribe to the topic until they are started. Now I could have some mediator actor to start them but

[akka-user] Re: Another Newbie Question -- Sending message to Millions of Cluster sharded actors.

Fair comment. :) On Wednesday, June 8, 2016 at 11:25:22 AM UTC-5, Ryan Tanner wrote: > > Unless you've profiled and found it to be a problem, worry about it later. > > On Wednesday, June 8, 2016 at 10:10:37 AM UTC-6, kraythe wrote: >> >> Sorry but i have another newbie q

[akka-user] Another Newbie Question -- Sending message to Millions of Cluster sharded actors.

Sorry but i have another newbie question. I have an actor that uses cluster sharding. There are potentially millions of these in the sytem concurrently and they maintain some state. At some point I would like to contact a million of these and ask them for their state to render information or

Re: [akka-user] Newbie question about storing ActorRef in a member variable

complicating the code for what might be a very small > optimization. From what I see here, I would *probably* just always use > ActorSelection for this code unless profiling indicated otherwise... > > On Tue, Jun 7, 2016 at 11:48 AM, kraythe <kra...@gmail.com > > wrote: >

[akka-user] Newbie question about storing ActorRef in a member variable

I am currently adding Akka to our existing system that currently does distributed programming with Executors in Hazelcast. Obviously he executor system is not scaling so I am currently working on how to convert it to an actor system. The temptation I have is to do the code below for my scoring

[akka-user] Cluster sharing without persistence? How to relay entity id to props?

I have an actor that I would like to use cluster sharing for but the thing is that the actor will restore its state from a database in the event of migration and so on. So there is no need to journal the messages and thus no need for Akka persistence. I have the vast majority of it sorted, but

[akka-user] Cluster Sharding + Hazelcast: Possible to dictate host for shard?

I am sorry I have been blitzing the group with questions but I have a rather snug deadline so I hope you will excuse the flurry. I currently have Hazelcast integrated into my system as a distributed memcache. I would like to use cluster sharding for some entity actors but would like to

[akka-user] Re: Considerations when pushing millions of messages through DistributedPubSub?

Good to know. I think I could batch the updates if need be. I will profile the load and see how it boils out. On Thursday, June 2, 2016 at 2:09:55 PM UTC-5, kraythe wrote: > > Greetings, > > I am wiring together some actors using distributed pub-sub. Basically I &

[akka-user] Considerations when pushing millions of messages through DistributedPubSub?

Greetings, I am wiring together some actors using distributed pub-sub. Basically I have actors that are broadcasting their state change. These updates will be in the millions and be received by multiple actor subscribers per node. Given that there are millions of these potential updates per

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

ious sort is being executed? > > Sent from my iPhone > > On 01 Jun 2016, at 22:43, kraythe <kra...@gmail.com > wrote: > > Perhaps, though honestly the entire problem scope is in the post, just > generically expressed. :) > > I cant be more specific bec

Re: [akka-user] Am I Reinventing the Wheel?

look at the relatively recent CRDT support, which is the closest > common cognate I can think of to this sort of approach... > > On Wed, Jun 1, 2016 at 9:25 PM, kraythe <kra...@gmail.com > > wrote: > >> They are updated from a DistributedPubSub topic. Each of them gets

Re: [akka-user] Am I Reinventing the Wheel?

: > > How are you coordinating state between logically-equal actors on different > physical nodes? > > On Wednesday, June 1, 2016 at 3:24:57 PM UTC-6, kraythe wrote: >> >> So the reason I didn't think this was cluster sharding is that I actually >> want these superv

Re: [akka-user] Am I Reinventing the Wheel?

So the reason I didn't think this was cluster sharding is that I actually want these supervisor actors (and their supervised children) to be REPLICATED on every node (they handle user requests). Basically if there is an actor with key 10, I want one actor with key 10 per node. I didn't want

Re: [akka-user] Am I Reinventing the Wheel?

Hmm, on one node? How Ok I will look at docs ... kind of thought I might be reinventing the wheel? Can I send to one router and have the message redirected to the actor with the right key ? On Wednesday, June 1, 2016 at 3:42:16 PM UTC-5, Konrad Malawski wrote: > > > I was working on a

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

t your initial description is too vague for direct help—that > sorting aspect is not really clear, at least to me. > > 1 jun 2016 kl. 20:04 skrev kraythe <kra...@gmail.com >: > > Pardon? I just said the users are observing the state and observing it > change in real time.

[akka-user] Am I Reinventing the Wheel?

I was working on a supervisor that lazy creates actors based on some key and then will forward messages to that actor. However, it just seems like I am doing something frightfully common. So I was wondering if anyone knows something in Akka that already does this and I should use that. I have

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

Pardon? I just said the users are observing the state and observing it change in real time. On Wednesday, June 1, 2016 at 10:31:16 AM UTC-5, √ wrote: > > So If no users are looking why does it need to be already updated? > > -- > Cheers, > √ > On Jun 1, 2016 4:44 PM, "

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

Users are observing their state via web pages. And no, it's not viable to the business to remove this ability, -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the

Re: [akka-user] Dependent Processing with Millions of Records without Backlogging?

rnate solutions do you have? (not worrying about implementation > for now) > > -- > Cheers, > √ > On May 31, 2016 18:31, "kraythe" <kra...@gmail.com > wrote: > >> I am seeking advice from those more experienced about some ideas for >>

[akka-user] Dependent Processing with Millions of Records without Backlogging?

I am seeking advice from those more experienced about some ideas for dealing with dependent processing. The use case is simple though I have to be a bit coy because of NDAs. I have some ideas myself but was hoping some of you with more experience than I could throw out some suggestions. I

[akka-user] com.github.romix.akka:akka-kryo-serialization_2.11 and AES Transform?

I have Been integrating this extension (which is mentioned in the Akka docs and is great) and I am having a problem. Basically it seems that when I enable the AES transform it generates a different serialized bytes each time which causes problems with hazelcast that uses the byte

[akka-user] Custom Serialization with FST or Kryo ?

Has anyone used FST Serialization[1] with their Akka messages? If so, how did it work out? I am debating using this or Kryo for serialization and FST seems to be faster and more "drop-in" compliant so i was curious if anyone had tried it. If you have tried Kryo before I would be interested in

[akka-user] Akka and RDBMS?

Greetings, I have a legacy app with an existing RDBMS and I would like to convert it to be an actor system. I have been researching this and came across Akka persistence but the documentation is thin on how to wire this into legacy backends. Furthermore, because of the high volume of legacy

Re: [akka-user] Implementing ACID style processing using Akka?

able to march into my company and say "I can solve all of our scalability problems." But until I overcome this issue, I am stuck. Any Advice? Any Options? Thanks -- Robert On Friday, May 13, 2016 at 1:17:16 PM UTC-5, rkuhn wrote: > > Hi Robert! > > 13 maj 2016 kl. 19:37

Re: [akka-user] Implementing ACID style processing using Akka?

of a "unit of work which spans domain objects". -- Robert On Friday, May 13, 2016 at 8:38:26 AM UTC-5, √ wrote: > > No, I mean if the bank reverses a payment which was previously accepted. > > -- > Cheers, > √ > On May 13, 2016 3:25 PM, "kraythe" <k

Re: [akka-user] Implementing ACID style processing using Akka?

t; On Fri, May 13, 2016 at 6:36 AM, Viktor Klang <viktor...@gmail.com > > wrote: > >> What will you do if the bank reverses the payment? >> >> On Thu, May 12, 2016 at 11:41 PM, kraythe <kra...@gmail.com >> > wrote: >> >>> I have a sys

Re: [akka-user] Implementing ACID style processing using Akka?

e bank reverses the payment? > > On Thu, May 12, 2016 at 11:41 PM, kraythe <kra...@gmail.com > > wrote: > >> I have a system that is a traditional DB centric app for the most part. >> However the data is loaded in a memcache for speed and ease of use. What I >> would b

  1   2   >