Re: [akka-user] Re: Akka Stream Getting Stuck (2.4.9-RC2)

Create a reproducer? -- Cheers, √ On Aug 6, 2016 1:18 AM, "tigerfoot" wrote: > I should add that when it fails it just locks the stream--nothing further > processed. No errors or other output is produced. > > On Friday, August 5, 2016 at 6:11:34 PM UTC-5, tigerfoot wrote:

[akka-user] Re: Akka Stream Getting Stuck (2.4.9-RC2)

I should add that when it fails it just locks the stream--nothing further processed. No errors or other output is produced. On Friday, August 5, 2016 at 6:11:34 PM UTC-5, tigerfoot wrote: > > I'm having a nasty issue I hope someone can help me with. > > I have some stream code like this: > >

[akka-user] Akka Stream Getting Stuck (2.4.9-RC2)

I'm having a nasty issue I hope someone can help me with. I have some stream code like this: val contentAssembly = Flow[CRec].map { crec => println("HERE!") val x = expression.render(crec.value).asInstanceOf[Message[OutputWrapper]] println("X is "+x) (crec,

[akka-user] Dynamically move proxied journal (PersistencePluginProxy) to another node

Hi, I have a usecase, where I'd like to be able to move the proxied journal from one cluster node to another. Looks like I can redirect all the journal clients using: *PersistencePluginProxy.setTargetLocation(someNewLocation)* But now on the cluster node, that has to host the journal I need to

Re: [akka-user] Akka Cluster (with Sharding) not working without auto-down-unreachable-after

On Fri, Aug 5, 2016 at 2:02 PM, Endre Varga wrote: > No, you are doing a great job explaining these! Maybe a guest blog post? > (wink, wink, nudge, nudge ;) ) > Thanks. Everything's on an "as time permits" basis -- most of my attention has to be on Querki -- but I'll

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

For anyone interested: turns out it's an error in the doc. Closing the listening side is *not* supposed to close the sending side. On Friday, July 29, 2016 at 6:28:14 PM UTC-7, Aditya Prasad wrote: > > Hi! > > I've got code like this: > >> val flow =

[akka-user] Re: Akka cluster node shutting down in the middle of processing requests

One more clue as to the cluster daemon's shutting itself down. Earlier in the logs (although prior to several successful requests being handled), I find this: [INFO] [08/05/2016 05:04:45.042] [ClusterSystem-akka.actor.default-dispatcher-5] [akka.cluster.Cluster(akka://ClusterSystem)] Cluster

[akka-user] Re: Akka cluster node shutting down in the middle of processing requests

Also, what does this message mean? I saw it earlier on in the logs: [DEBUG] [08/05/2016 05:04:50.450] [ClusterSystem-akka.actor.default-dispatcher-17] [akka://ClusterSystem/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%4010.0.3.176%3A2552-6] unhandled message

[akka-user] Akka cluster node shutting down in the middle of processing requests

Our akka-cluster-sharding service went down last night. In the middle of processing akka-http requests (and sending these requests to a sharding region for processing) on a 10-node cluster, one of the requests got an "ask timeout" exception: [ERROR] [08/05/2016 05:04:51.077]

Re: [akka-user] Akka Cluster (with Sharding) not working without auto-down-unreachable-after

On Fri, Aug 5, 2016 at 12:04 AM, Justin du coeur wrote: > It does do reassignment -- but it has to know to do that. Keep in mind > that "down" is the master switch here: until the node is downed, the rest > of the system doesn't *know* that NodeA should be avoided. I

Re: [akka-user] Akka Cluster (with Sharding) not working without auto-down-unreachable-after

Yes, thanks. I'll take a look at the default implementation and explore possible other implementations. I suspect, however, that the solution I've now implemented to "down" unreachable nodes if the AWS/ECS cluster says they are no longer there, will address my issues. On Friday, August 5,

Re: [akka-user] Akka Cluster (with Sharding) not working without auto-down-unreachable-after

Thanks Justin. Makes good sense. And I believe you've explained the lock up -- the shard coordinator singleton was probably on the unreacheable node (actually, it must have been, because prior to the second node's coming up, the first node was the only node) and since the cluster-of-two

Re: [akka-user] What is idiomatic way to share state on a local node.

This approach does not work with complex data structures. They should be composable, each part separately addressable, other actors should be able to subscribe to the state changes individually. There should be a way to create read-only view for a data and so on. Approach "just create actor

[akka-user] [ANNOUNCE] Akka 2.4.9-RC2 released!

Dear hAkkers, We—the Akka committers—are pleased to announce the availability of Akka 2.4.9-RC2. This release does not change much over the previous Release Candidate, except fixing one OSGi plugin induced packaging problem which might have caused compilation errors, see issue #21105

Re: [akka-user] Stashing vs Scala Collection

Hi, for the usecase you mentioned, it makes more sense for me to use a collection, as you will be able to process exactly as many stashed requests as you have available resources. You will also be able to track the number of stashed resources and deal with overflow more easily. On Thu, Aug 4,

Re: [akka-user] Distributed usage: 3rd party connectors (instead of TCP)

Hi Michael, I would assume that you want to implement network communication API based on actors as it is done with TCP and UDP in Akka Io module . Feel free to look at the source code

Re: [akka-user] What is idiomatic way to share state on a local node.

One of the simplest solutions would be to model it as an actor itself. A fun challenge would also be to model backgammon board based on a Conflict Free Replicated Data type. If you solve that, then you could use Akka Distributed Data

Re: [akka-user] [akka-stream] How to emit the newest element every n seconds?

Hi. You were quite close. Instead of buffer.drophead use conflate which is a rate detached operation. That allows upstream before conflate progress faster than downstream after the conflate. Source .unfold(0) { e => Some((e + 1, e)) } .conflate[Int] { case (_, e) => e } .throttle(1,

[akka-user] What is idiomatic way to share state on a local node.

For example, we would like to model the backgammon game with akka actors. Both players are actors (either human or AI), there is also an actor that rules the board and determines dice rolls for players. They all share the single board. What is idiomatic way to have access to the board and to

[akka-user] Re: explanation of pickMaxOfThree

Hi Gitted, I am a newbie and not much of a scala guy The example referenced is for producing the largest of the 3 numbers input. zip1's zipwith is using 2 of the 3 numbers as input and producing one output that is the larger of the 2 numbers. zip2's zipwith is going to use the third

Re: [akka-user] Re: Multipart Fileupload problem with Akka 2.4.8 and 2.4.9-RC1

Ah ok that explains a lot. No worries, thanks for the reply. I appreciate it! On Friday, August 5, 2016 at 5:49:14 AM UTC-4, Konrad Malawski wrote: > > Hi Scott, > OSGi messed up our RC1 release. > Sorry for the trouble, though glad we did the RC which is there for > finding such issues before

Re: [akka-user] Re: Multipart Fileupload problem with Akka 2.4.8 and 2.4.9-RC1

Hi Scott, OSGi messed up our RC1 release. Sorry for the trouble, though glad we did the RC which is there for finding such issues before we release a stable version. The bug is explained in https://github.com/akka/akka/issues/21105 and I've fixed both root cause and sbt plugin so we'll never have

[akka-user] Re: Multipart Fileupload problem with Akka 2.4.8 and 2.4.9-RC1

Hey, sorry but I have yet another stupid question. All of my dependencies seem to be correct now, but when I switch from version 2.4.8 to 2.4.9-RC1, I get this error: [ERROR] error: missing or invalid dependency detected while loading class file 'Unmarshaller.class'. [INFO] Could not access

[akka-user] Distributed usage: 3rd party connectors (instead of TCP)

Hi! i'm new to akka. Newer used it. Only played with activator. I think akka and especially the actor model would fit very very nicely on a new release of a project i'm working on. It's a distributed communication network where nodes are communicating via: * TCP (not really used currently). *

Re: [akka-user] Akka Cluster (with Sharding) not working without auto-down-unreachable-after

You can however implement your own akka.cluster.sharding.ShardCoordinator.ShardAllocationStrategy which will allow you to take whatever you want into account, and deal with the consequences thereof ofc ;) -- Johan On Friday, August 5, 2016 at 12:04:12 AM UTC+2, Justin du coeur wrote: > > It

[akka-user] Re: Using TestProbe to automate test by replying automatically just to ensure that the test goes

I do not understand the following sentence either: The run method must return the auto-pilot for the next message, which may be KeepRunning to retain the current one or NoAutoPilot to switch it off. 1 - what is the current one referring to here: the next message or the auto-pilot ? To me,

[akka-user] Re: Using TestProbe to automate test by replying automatically just to ensure that the test goes

I have seen it, but i simply don't understand it at all. 1. val probe = TestProbe() 2. probe.setAutoPilot(new TestActor.AutoPilot { 3. def run(sender: ActorRef, msg: Any): TestActor.AutoPilot = 4. msg match { 5. case "stop" ⇒ TestActor.NoAutoPilot 6. case x ⇒ testActor.tell(x,

Re: [akka-user] Stream within Actor Supervision

Stream errors are *in* the stream. It does not blow up the Actor, nor should it. What's your use case? -- Konrad `ktoso` Malawski Akka @ Lightbend On 5 August 2016 at 09:31:16, Gary Struthers (agilej...@earthlink.net) wrote: I think I understand. The

Re: [akka-user] Stream within Actor Supervision

I think I understand. The other part of my question is when a stream is within an actor. If the stream has an error where I want the enclosing actor to stop how do I do that? Also, any advice on testing error handling? -- >> Read the docs: http://akka.io/docs/ >>

[akka-user] Re: Using TestProbe to automate test by replying automatically just to ensure that the test goes

Defining a receive for TestProbe won't do anything. Instead take a look at Auto-Pilot for the behavior that you want: http://doc.akka.io/docs/akka/current/scala/testing.html#Auto-Pilot On Thursday, August 4, 2016 at 3:59:50 PM UTC-7, Maatary Okouya wrote: > > I am trying to get a test probe to

Re: [akka-user] Stream within Actor Supervision

If you write *custom* GraphStages, then *you* need to decide what supervision means in that context – then is supports it: https://github.com/akka/akka/commit/5382014133d01cd38729d731763841680f93a42c#diff-3203199ba389ee802eef94486f26dc88R41 -- Konrad `ktoso` Malawski Akka @