Arnout,
I have a single type of actor that I create that will be not be
instantiated but available to instantiate on a server cluster, lets call,
ClusterX. That cluster can have two seed nodes and grow from 1 to 1000
member nodes. These actors will have a key-value pair as state and when the
Any thoughts?
On Thursday, July 6, 2017 at 2:23:50 PM UTC-7, Jeff wrote:
>
> Here is a strawman program which illustrates the issue I am having
>
> trait RequestBuilder {
> type Out
>
> def complete(p: Promise[Out]): Unit
> }
>
> def makeRequest(in: RequestBuilder): Source[(RequestBuilder,
>
Hi Johannes,
perfect, thanks for the insight. I think we can work with that.
Cheers,
Michael
Am Montag, 10. Juli 2017 16:55:55 UTC+2 schrieb johannes...@lightbend.com:
>
> Hi Michael,
>
> On Monday, July 10, 2017 at 9:01:00 AM UTC+2, Michael Pisula wrote:
>>
>> As far as I saw from the source cod
The "power mode” ;-)
On 11 July 2017 at 00:02:12, Justin du coeur (jduco...@gmail.com) wrote:
Oh, sweet -- ExtensibleBehavior looks enormously useful...
On Mon, Jul 10, 2017 at 9:29 AM, Konrad 'ktoso' Malawski
wrote:
> Once I wrote the response I though that for using the library directly
> y
Oh, sweet -- ExtensibleBehavior looks enormously useful...
On Mon, Jul 10, 2017 at 9:29 AM, Konrad 'ktoso' Malawski
wrote:
> Once I wrote the response I though that for using the library directly
> you'll also want to know about the possibility to implement:
>
>
> /**
> * Extension point for im
Hi,
Thanks for the answers!
Michal,
Your approach seems most appropriate for my case as it dedups *and* handles
late records. Your point on losing messages in the map upon restart after a
failure, is very valid. One way of handling this is to have checkpoints at
window-level.
Roughly speaking,
Hi Michael,
On Monday, July 10, 2017 at 9:01:00 AM UTC+2, Michael Pisula wrote:
>
> As far as I saw from the source code, it could point to a problem with
> header parsing, but I am not exactly sure what could cause the problem.
>
The place in the code is actually misleading, as it the error is
Once I wrote the response I though that for using the library directly
you'll also want to know about the possibility to implement:
/**
* Extension point for implementing custom behaviors in addition to the existing
* set of behaviors available through the DSLs in [[akka.typed.scaladsl.Actor]]
Akka Typed is still not quite "done" so missing or undecided upon APIs may
still be here and there.
That's one of them, so I opened a ticket to discuss and decide what to do
about it in Typed.
https://github.com/akka/akka/issues/23326
Having that said, you can always just directly use the loggi
Hello Ram,
ClusterClient/ClusterReceptionist are relatively low-level tools.
I see you're already familiar with Cluster Sharding. Wouldn't that be a
possible solution for "creating an actor somewhere on the cluster without
the original requestor having to bother where it needs to be created"?
If
Hello,
I'm using alpakka 0.10, akka 2.5.3.
When using S3 multiUpload on a slow connection, I'm getting an error
sometimes:
java.lang.RuntimeException: Cannot find etag
at
akka.stream.alpakka.s3.impl.S3Stream.$anonfun$chunkAndRequest$5(S3Stream.scala:218)
at scala.Option.getOrElse(Option.sc
Hi guys,
Long time no see :-)
We seeing a strange exception in the logs of our new Akka Http app in
production. The Exception is an EntityStreamException with the cause
message "entity stream truncation". I could not find any helpful
information regarding that exception here in the list or in
12 matches
Mail list logo