[akka-user] akka-1.3.1.xsd schema location

A very old application leveraging akka-camel-1.3.1 is now failing with the following error: XmlBeanDefinitionReader.java:396:in `doLoadBeanDefinitions': org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 126 in XML document from class path resource [camel-context.xml] i

Re: [akka-user] akka-1.3.1.xsd schema location

Hi there, you could get them from here: https://github.com/akka/akka.github.com/tree/968159d916d9a54c5d247c5b228398e1e0d43d68 (old version of what was the website, and had all these files). — Konrad `kto.so` Malawski Akka @ Lightbend On 1 August 2017 at 17

[akka-user] Akka-HTTP: How does backpressure work with Futures and execution contexts?

Hi all, I am just trying out akka-http and haven't been able to find much information about how backpressure works when we use futures and run operations async. For example, if I create a REST API with a route that looks like this: ``` val route = (path("users") & post & entity(as[NewUser]))

[akka-user] Sharding coordinator comms issues running on Kubernetes

Hi, Seeing some strange issues running Cluster Sharded actors in a kubernetes environment. We are currently running a 3 node akka cluster, with our app running within a docker container within a kubernetes stateful set (similar to the akka-seed set described here

[akka-user] Re: Sharding coordinator comms issues running on Kubernetes

As a follow up, I've now just ruled out any kubernetes networking issue by recreating the same behaviour running 3 nodes via docker-compose instead - again it only works if an API call hits the first node in seed-nodes list. On Tuesday, 1 August 2017 14:11:07 UTC+1, Stephen Kennedy wrote: > > Hi

Re: [akka-user] Re: Sharding coordinator comms issues running on Kubernetes

Looks like ClusterSharding.start is missing at startup of api-0. Are you sure that you do that when the ActorSystem has been started and not lazily on first request? Enable debug level logging and you should see what it is doing. You should see log entries in api-0 at startup. /Patrik tis 1 aug.

[akka-user] Re: Akka Camel and Akka Streams

Martin, Is there an Ack or Nack/Status.Failure mechanism with the new streamz camel api like in the akka-camel actor Consumer api? Thanks, Sam On Thursday, July 13, 2017 at 4:16:52 AM UTC-4, Andreas Gies wrote: > > Hi, > > thanks for the pointer to the Camel docs. I knew I had a blindspot > s

Re: [akka-user] Re: Sharding coordinator comms issues running on Kubernetes

Thanks for the prompt reply. As hoped it has instantly made me realize the error of our ways. Our application bootstrap code was over using lazy val's, so as you suggest we weren't actually calling ClusterSharding.start until that node needed the ActorRef. So I can further my understanding, co

[akka-user] problem with pinned dispatcher

Hello, I'm trying to use PinnedDispatcher using the following configuration (in application.conf): app { pinnedDispatcher { type = "PinnedDispatcher" executor = "thread-pool-executor" thread-pool-executor.allow- core-timeout = off thread-pool-executor {

[akka-user] Distributed Data - OversizedPayloadException even when splitting ORMultiMap into many keys

Hi, I currently am using using ~100 instances of ORMultiMap[Int, Int] by the following code and am constantly adding/deleting elements (~200/sec) in the value sets. I have delta-crdt enabled as well. def hash(key: Int, mod: Int) = { key % mod } def mapKey(key: Int) = { ORMultiMapKey[Int,

[akka-user] Re: DistributedPubSub sending messages to DeadLetter

Hi Johan Thanks for your response. I'll try implementing it and submitting a PR. Best Regards Rafał W dniu piątek, 28 lipca 2017 09:11:49 UTC+2 użytkownik Johan Andrén napisał: > > In many cases it may be a sign that something is wrong when there are no > subscribers, for example because topic n

Re: [akka-user] Consuming akka-streams service via Javascript

Will back pressure still work over http, without a library on the Javascript side that uses the same protocol as akka-streams? On Monday, July 31, 2017 at 6:59:47 PM UTC-6, Konrad Malawski wrote: > > Hi there, > In general “streaming consumption" of such API can be simplified to “start > working

Re: [akka-user] Consuming akka-streams service via Javascript

Yes, since we translate reactive streams back-pressure onto TCP flow control which has tot be handled (and is handled) by anything that speaks TCP, which includes any HTTP call. — Konrad `kto.so` Malawski Akka @ Lightbend On 2 August 2017 at 02:35:35, B Wil

Re: [akka-user] problem with pinned dispatcher

«Note that it’s not guaranteed that the *same* thread is used over time, since the core pool timeout is used for PinnedDispatcher to keep resource usage down in case of idle actors. To use the same thread all the time you need to add thread-pool-executor.allow-core-timeout=off to the configuration

Re: [akka-user] problem with pinned dispatcher

I don't think that is the right way to define the dispatcher for router pool. See docs http://doc.akka.io/docs/akka/current/scala/routing.html#configuring-dispatchers /Patrik tis 1 aug. 2017 kl. 20:40 skrev Viktor Klang : > «Note that it’s not guaranteed that the *same* thread is used over time

Re: [akka-user] Re: Sharding coordinator comms issues running on Kubernetes

You're welcome. Yes, you are supposed to register (start) the sharding on all nodes (or nodes with a certain role). The coordinator is a Cluster Singleton, i.e. running on oldest node (when you have started it). Other nodes try to register to the coordinator at the oldest node. /Patrik tis 1 aug.

[akka-user] Re: how to bind each actor in a pool to a thread

I'm not experienced with configuring routers from config, since I prefer using code, but as far as I understand you did set a dispatcher for the /master/worker - the router, not for it's routees - the actual worker actors. If you print the thread name in constructor an in receive of workers you

[akka-user] Flow.fromSinkAndSource and backpressure

I didn't see much in the documentation, so I thought I'd ask. If I have a Sink.actorRef and a Source.actorRef, and I combine them using Flow.fromSinkAndSource, does this somehow propagate backpressure? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

[akka-user] Re: how to bind each actor in a pool to a thread

Hello, Thank you for your help. After reading your comment ("the router, not for it's routees") I remembered about actor groups (as opposed to pools). I defined a common pinned dispatcher (in application.conf, directly under "akka" element): pinnedDispatcher { type = "PinnedDispatch

Re: [akka-user] problem with pinned dispatcher

I got this to work by defining actor group, see my other post ("how to bind each actor in a pool to a thread"). Thanks, M On Tuesday, August 1, 2017 at 12:31:36 PM UTC-7, Patrik Nordwall wrote: > > I don't think that is the right way to define the dispatcher for router > pool. See docs > htt

[akka-user] Flow.fromSinkAndSource and backpressure

Nope. More so, completion of one of them would not cause completion of another and flow itself. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives: https:/

Re: [akka-user] Flow.fromSinkAndSource and backpressure

Hi Jeff, Alexey, that’s not correct, back-pressure works there - because it has to: it is enforced by the reactive-streams protocol that we follow by heart in Akka streams. Yes, back-pressure works, the one sentence explanation would be: “independently on each side of the newly constructed flow”.

Re: [akka-user] Flow.fromSinkAndSource and backpressure

Hi Konrad, Jeff was asking about 'backpressure propagation'. From my understanding that means that when source wasn't pulled, sink would not pull. And that's not how it works as you already mentioned. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >

Re: [akka-user] Flow.fromSinkAndSource and backpressure

Good point, I missed that word in the question - thanks and sorry about that :) A full clarification was still useful I hope though, cheers! — Konrad `kto.so` Malawski Akka @ Lightbend On 2 August 2017 at 15:45:51, Alexey Shuksto (seig...@gmail.com) wrote: