cpu*
> *metrics-selector = mix*
> *#*
> *routees.paths = ["/user/expEvaluationBackend"]*
> *nr-of-instances = 100*
> *cluster {*
> * enabled = on*
> * use-role = backend*
> * max-nr-of-instances-per-node = 3*
> * allow-local-routees =
s://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroup
the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr.
ompare.sources.IceUtilsDifference" =
>> kryo"org.iceengine.compare.sources.ListWritter" =
>> kryo"org.iceengine.compare.sources.LogWriter" =
>> kryo"org.iceengine.compare.sources.SqlWritter" =
>> kryo"org.iceengine.compare.sources.SSSh
\Users\admin\AppData\Local\Temp.
> how to clean up Aeron files ?
>
> On Wednesday, May 17, 2017 at 12:46:54 PM UTC+5:30, Patrik Nordwall wrote:
>>
>> Performance debugging/tuning is not something I can help with in free OSS
>> support. We would be able to do that
s from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
--
Pa
rformance is getting hit ( when i am
> processing big file). Is there any way in aeron configure application so
> that it won't create that temporary file???
>
> On Wednesday, May 17, 2017 at 4:52:12 PM UTC+5:30, Patrik Nordwall wrote:
>>
>> When you use the embe
and I mean 10,000 bytes message, ofc
On Thu, May 18, 2017 at 10:42 AM, Patrik Nordwall wrote:
> I don't think the bottleneck is in Artery/Aeron. We have measured very
> good throughput such as
>
>- 100 bytes message: 689,655 msg/s, 68,965,517 bytes/s
>- 10, bytes
A few a know about: rsyslog, Splunk, Lightbend ConductR
/Patrik
fre 19 maj 2017 kl. 12:47 skrev Evgeny Shepelyuk :
> Hello,
>
> We're using ELK for our Docker based services and currently it's quite
> useful for collecting and analyzing logs.
> There's another option https://www.graylog.org - it
run: 5
> [JVM-2] Suites: completed 1, aborted 0
> [JVM-2] Tests: succeeded 5, failed 0, canceled 0, ignored 0, pending 0
> [JVM-3] [WARN] [05/22/2017 16:31:21.682]
> [ServiceRegistrySpec-akka.actor.default-dispatcher-4]
> [akka://ServiceRegistrySpec/system/endpointManager/
> re
>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Go
ote-dispatcher-8] [akka.tcp://VotingServiceSpec@
> localhost:56966/system/remoting-terminator] Shutting down remote daemon.
> [JVM-3] [INFO] [05/22/2017 16:31:31.989] [VotingServiceSpec-akka.
> remote.default-remote-dispatcher-8] [akka.tcp://VotingServiceSpec@
> localhost:56966/sys
> Thanks,
> Mainak
>
> On Wed, May 24, 2017 at 8:24 AM, Patrik Nordwall <
> patrik.nordw...@gmail.com> wrote:
>
>> That's interesting. I see the same problem when running that example. It
>> shouldn't be much data involved there. I have created issue
>
>> which pattern would be best to resolve this issue and faster?
>>
>>
>> On Wednesday, 24 May 2017 17:54:11 UTC+5:30, Patrik Nordwall wrote:
>>>
>>> You have to implement some flow control, such as as using the "Work
>>> Pulling" pattern
>
ing emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
One "way" to down a node is to restart it and join the cluster again with
same hostname:port. It will have a new UID and that is enough evidence for
automatic down of the old incarnation.
I agree with Justin, though. You probably need something more than just
restarting for proper downing. E.g. wh
Can't you use Source.queue? Backpressure can be maintained by piping the
result of the future back to an ordinary actor.
/Patrik
lör 27 maj 2017 kl. 16:29 skrev Richard Rodseth :
> In case it helps:
>
> https://groups.google.com/d/topic/akka-user/AgVHHnl9ub4/discussion
> https://github.com/akka/a
It can be many reasons for delayed heartbeat messages.
- GC. Enable gc logging and try to correlate.
- Slow serialization/deserialization of your application messages,
especially if you send many messages in a burst
- Running blocking actors/tasks on the default dispatcher
/Patrik
tors 25 maj 201
Thanks. Our thinking was that http://akka.io/docs/ would be the landing
page for all docs including such links. Not enough?
/Patrik
sön 28 maj 2017 kl. 15:26 skrev Mike Nielsen :
> Congratulations, team, on the new Akka documentation site. It looks good!
>
> By way of a minor enhancement, would
ut the possibility that there may be more runnable
> examples using ScalaFiddle!
>
> Well done and thank you for taking the time on a Sunday to reply!
>
> Warm regards,
>
> Mike
>
> On Sun, May 28, 2017 at 9:33 AM, Patrik Nordwall <
> patrik.nordw...@gmail.com> wrote
lectiveDynamicAccess.getClassFor(ReflectiveDynamicAccess.scala:20)
> at
> akka.actor.ReflectiveDynamicAccess.createInstanceFor(ReflectiveDynamicAccess.scala:38)
> ... 54 more
>
>
> how can resolve this error ?
>
>
>
>
>
> --
> >>>>>
---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to
d.
> All comments welcome.
>
> Happy to work on a PR if this approach is deemed valid.
>
> Thanks,
>
> Michał
>
> On 10/03/17 09:32, Patrik Nordwall wrote:
>
> Such asymmetric splits can be problematic, because the unreachability
> information is spread via
By the way, have you tried to reply (send the reply with ordinary tell / !)
andThen? See example in
http://doc.akka.io/docs/akka/current/scala/persistence.html#persistent-fsm
On Tue, May 30, 2017 at 2:27 PM, Patrik Nordwall
wrote:
> I see what you mean. One way around it is to:
>
quot; group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For mor
You should never try to override properties defined in one reference.conf
in another reference.conf. The order is undefined and you will not know
what you are running. In other words, Akka properties should be defined in
application.conf, never in reference.conf outside Akka.
The purpose of refere
I would guess you are looking for MemberRemoved. That should cover both the
graceful leaving case and unexpected crash followed by downing case.
/Patrik
ons 31 maj 2017 kl. 12:01 skrev David :
> Apparently I can subscribe to akka.cluster.ClusterEvent.MemberLeft, which
> provides the information I
You must have more than one node in the seed-nodes list, otherwise it will
just join itself instead of first trying to join the existing cluster.
/Patrik
tors 1 juni 2017 kl. 15:54 skrev fady zohdy :
> i have a multiple node akka cluster running with single seed node running
> on static ip and po
http://doc.akka.io/docs/akka/current/scala/general/remoting.html#peer-to-peer-vs-client-server
Sorry for short answer
/Patrik
fre 2 juni 2017 kl. 09:35 skrev Manfred Bergmann :
> Hello.
>
> I need some advice.
>
> The following situation (Akka 2.5.2):
>
> I have an ActorSystem on one host (host0
That sounds very strange, and interesting. Do you have a way to reproduce
it that you can share? Any interesting logging if you enable debug log
level?
/Patrik
fre 2 juni 2017 kl. 21:51 skrev Joseph Mansigian <
joseph.c.mansig...@gmail.com>:
> I have an application that uses remote addressing exc
emails from it, send an
>> email to akka-user+unsubscr...@googlegroups.com.
>> To post to this group, send email to akka-user@googlegroups.com.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>
cally or is this a limitation?
>
> Mainak
>
> On Wed, Jun 7, 2017 at 6:40 AM, Patrik Nordwall > wrote:
>
>> Note that the intention is to use the local `Replicator` so there is not
>> much point in delegating the message with a router to remote node, unless
>&
e-started on node termination. Not a perfect solution, by far.
>
> So, yes. Akka IO or HTTP is probably better suited for this particular use
> case.
>
> However, I'm still wondering if there is a chance to get along with Akka
> remoting.
>
>
> Manfred
>
>
&
.
The complete list of closed issues can be found on the 2.4.19
<https://github.com/akka/akka/milestone/112?closed=1> milestone on github.
For this release we had the help of 5 committers – thank you all very much!
commits added removed
5318 142 Patrik Nordwall
y, we are exploring the impact of
>> controlled locality for remote actors.
>>
>> Thanks,
>> Mainak
>>
>>
>> On Thu, Jun 8, 2017 at 2:59 AM, Patrik Nordwall <
>> patrik.nordw...@gmail.com> wrote:
>>
>>> I think resizer is only for loca
ceived this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to ak
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed
which lately have been around merging Java
and Scala documentation content.
commits added removed
27 2664 6189 Richard Imaoka
16302 756 Arnout Engelen
12731 84 Patrik Nordwall
10301 368 Johan Andrén
4 54 18 Konrad `ktoso` Malawsk
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Goog
le.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/fa
ogle Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups
That is not supported. You have to filter in the destination (or put
another actor in-between).
/Patrik
tors 22 juni 2017 kl. 08:44 skrev Gajendra Naidu :
> Just wondering if there is a way in AKKA - DistributedPubSub to subscribe
> messages with some filter like take the function as a parameter.
You want to use Backoff supervision here, and that is actually an ordinary
actor that takes care of the supervision for one other actor. You have to
use a Backoff supervisor for the manager an one for each child. It only
supports one-for-one.
/Patrik
tors 22 juni 2017 kl. 07:46 skrev Muthukumaran
I'd recommend that you create a minimized example without addition external
dependencies. Then I or someone can run it and perhaps see what is the
culprit.
/Patrik
fre 23 juni 2017 kl. 00:15 skrev Kilic Ali-Firat :
> Like you said, 2000 msg / sec is really relly slow. The reactive Kafka
> con
at 4:20 PM, Gajendra Naidu
wrote:
> Patrik
>
> Was there any technical reason why it is not supported? if no, I can
> contribute to add this functionality.
>
> Gajendra
>
> On Thursday, June 22, 2017 at 10:27:40 PM UTC+5:30, Patrik Nordwall wrote:
>>
>> That is
: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to akka-user+...@googl
They are allocated independent of each other and since that can be in
different order they may end up on different nodes.
You can implement your own shard allocation function. The result is
returned in a Future so it can delegate the decision to an actor with ask.
That actor can be the same for bo
:28 PM, Andrey Ilinykh wrote:
>
>
> On Sunday, July 2, 2017 at 12:45:38 AM UTC-7, Patrik Nordwall wrote:
>>
>> They are allocated independent of each other and since that can be in
>> different order they may end up on different nodes.
>>
>> You can implement
ubscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit thi
I think Eclipse has a plugin that understands a maven pom and adds the
needed dependendencies to the project. You can import a maven project.
In this case you are missing a transitive dependency. Trying to
add/maintain those manually will be a pain so I suggest that you let the
IDE/plugin handle i
gt; To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://group
er
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-u
Hi Mainak,
Thanks for the background to your questions. It sounds like interesting
research.
I would not go down the path of pool routers. It's pretty difficult to
implement custom things with them and we are slowly moving away from remote
deployment (used by pools). E.g. Akka Typed will not supp
Hm, interesting. Even if the classTag is causing the problem there might be
something more here.
permits must not be negative
java.lang.IllegalStateException: permits must not be negative
at
akka.persistence.RecoveryPermitter.akka$persistence$RecoveryPermitter$$returnRecoveryPermit(RecoveryPermitt
E.g. at startup the actor might be in initialization mode, e.g. waiting for
reply from external service, and then changing behavior to active (with
different state variables). You can even switch between mutable and
immutable.
In untyped actors this is supported with context.become
/Patrik
ons 19
I don't know about the serialization. Sounds strange.
However, note that consistent hashing pool often doesn't make much sense in
a cluster, since routees of the pools are not shared between different
nodes. Group router is typically better, or Cluster Sharding if more strict
routing is needed.
/
erializer.
> will check it in the office tomorrow if using one of them reduces the time
> spent there.
>
>
> On Saturday, July 22, 2017 at 2:26:31 PM UTC+3, Patrik Nordwall wrote:
>
>> I don't know about the serialization. Sounds strange.
>>
>> However, note th
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.
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
ired to call
> ClusterSharding.start? Reading docs a bit more it sounds like that is the
> case, as if we wanted to only run on a sub-group of nodes we should use
> roles.
>
> Thanks again for helping out.
>
> On Tuesday, 1 August 2017 14:56:33 UTC+1, Patrik Nordwall wrote:
Perhaps try to define props factory method in companion object, see
recommended practises in docs
http://doc.akka.io/docs/akka/current/scala/actors.html#creating-actors
/Patrik
lör 5 aug. 2017 kl. 08:07 skrev 周梦想 :
> thank you. it is cause by spark streaming closure, if it reference to
> member v
ogle Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akk
email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
--
Patrik Nordwall
Akka Tech Lead
Ligh
ould like to thank Thomas Szymanski for bringing this issue to our
attention.
Credits
For this release we had the help of 5 committers – thank you all very much!
commits added removed
2167 128 Patrik Nordwall
2 10 10 Thomas Szymanski
1174 21 Kirill Ya
your
applications and libraries when doing this update.
We would like to thank Thomas Szymanski for bringing this issue to our
attention.
Credits
For this release we had the help of 47 committers – thank you all very much!
commits added removed
18 1537 2328 Arnout Engelen
1
It should work with .async after groupBy. It can still be same thread. To
see it (different threads) you might have to add a sleep in the map.
/Patrik
sön 13 aug. 2017 kl. 12:35 skrev Alexey Shuksto :
> Hello there,
>
> Is there a way to guarantee that subflows after '.groupBy(..)' operation
> wo
iving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
-
tentHashingGroup) to handle that: I'd have
>> to death-watch actor instances to manage this Replicator's lifecycle. Is
>> this approach good practice?
>>
>> Thanks
>> Igor
>>
> --
> >>>>>>>>>> Read the docs: http://akka
ole_i? If so, they can simply read the
> data if they are on the node with the right role.
>
Yes they can read instead, but then you would need to know when to read.
Perhaps you do that for each request, that would also work.
>
> Thanks!
> Igor
>
> On Wednesday, August 16,
>
> On Wednesday, August 16, 2017 at 4:11:09 PM UTC+3, Patrik Nordwall wrote:
>
>>
>>
>> On Wed, Aug 16, 2017 at 1:28 PM, Igor Baltiyskiy
>> wrote:
>>
>>> Hello Patrik,
>>>
>>> thanks for the reply. Could you please clarify a few p
Hi Kiran,
There is nothing special in Akka for jdbc access. You would use it as in any
other Java program. However, since jdbc is a blocking API you need to carefully
manage that if used from inside Actors. See
http://doc.akka.io/docs/akka/current/java/dispatchers.html#blocking-needs-careful-ma
n
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
--
Patrik Nordwall
Akka Tech Lead
Lightbend
It may change the order. You can use mapAsync if you want to preserv the order.
/Patrik
> On 26 Aug 2017, at 17:11, Ori Popowski wrote:
>
>
> Hi,
>
> Say that I have a stream with a consecutive integers source (1, 2, 3 ...),
> and assume that toString returns a Future[String]:
>
> source ~>
.google.com/d/optout.
>
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Sear
If you only use Distributed Data you could run without downing.
If you want to automate restart and rejoin of crashed jvm you can do that by
using fixed hostname and port. Joining a node with same hostname port as
existing member (different uid) will trigger down/removal of old incarnation so
t
That would be a bug. Please create an issue. I would guess that the problem is
in system ? and not in the child. Did you add logging in the guardian also?
/Patrik
> On 31 Aug 2017, at 14:18, 'Kostas kougios' via Akka User List
> wrote:
>
> I am using the ask pattern to
>
> system ? (ref =>
mapAsync is the Swiss army knife.
Use ask and the actor replies when persist is done.
/Patrik
> On 1 Sep 2017, at 08:44, techland.co...@gmail.com wrote:
>
> Hi, is anyone else trying to use the new Akka Streams with Akka
> Persistence? Has anyone created any code examples yet showing how to use
>
Jdk 8, Scala 2.12, Akka 2.5.4
I suggest that you start at http://akka.io/try-akka/ to create a template
project
/Patrik
> On 1 Sep 2017, at 17:07, Joseph Mansigian
> wrote:
>
> Hello to Akka Developers,
>
> Can someone suggest to me a current compatible triad of java, scala, akka
> versio
If A and B are on the same node (jvm) this doesn't make much sense.
If that node crashes and the redelivery is continued by another node (restarted
jvm) then the ActorRef to A would be be obsolete.
AtLeastOnceDelivery would be used as a safe hand-off between A and B, but A
should not have to wa
Are they able to connect at all?
Perhaps this is what you need to configure (see NAT section)
http://doc.akka.io/docs/akka/current/java/remoting.html#remote-configuration
That feature was introduced in Akka 2.4
/Patrik
> On Aug 30, 2017, at 14:57, Rodrigo Silva wrote:
>
> Hi Konrad, thanks for
gt; email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
--
Patrik Nordwall
Akka Tech Lead
Lightbe
Sorry, I will not find time to write example. See documentatio, section
Integration with actors
/Patrik
> On 2 Sep 2017, at 09:16, tech land wrote:
>
> excuse Me ! can write a short or simple Sample ?? because Im beginer in Akka
>
>
>> On Fri, Sep 1, 2017 at 1:3
ubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.c
t; group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For
ions.html#actorsubscriber
>
> On Tue, Sep 5, 2017 at 1:19 PM, Patrik Nordwall > wrote:
>
>> Sorry, I will not find time to write example. See documentatio, section
>> Integration with actors
>>
>> /Patrik
>>
>> On 2 Sep 2017, at 09:16, tech land wr
A lot of things have been fixed since that version. Try latest. See readme for
version info.
/Patrik
> On 6 Sep 2017, at 16:19, Sergei Akhapkin wrote:
>
> Hi folks,
>
> I've a question: did someone experienced Akka persistence query on Cassandra
> to be stalled without any symptoms ?
>
> My
es: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@go
the actor will be stopped and the stream is
failed.
If the future is completed with failure the pipeTo will send that as
Status.Failure, which is taken care of.
/Patrik
>
>
> On Thursday, September 7, 2017 at 9:50:26 AM UTC+3, Patrik Nordwall wrote:
>>
>> A lot of things h
Hi Sebastian,
Validation should be done before persist, and your code is correct.
Exceptions from validation should not be thrown, your conclusion is correct.
Regarding unforeseen bugs, NPE, it can be better in a production system to
survive also that by restarting (perhaps it was just a corner c
an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
--
Patrik Nord
is exactly what I needed. Thanks Patrik!
>
> On Sunday, September 10, 2017 at 10:50:08 AM UTC-4, Patrik Nordwall wrote:
>>
>> Perhaps take a look at this example: https://github.com/ak
>> ka/akka-distributed-workers-scala
>> It has recently been updated, and the guide is
GC tuning is typically very application specific. I'd recommend to start with
setting ms/mx heap to 2G and then profile and monitor the application. GC
logging flags are useful to enable.
/Patrik
> On 14 Sep 2017, at 14:36, Kilic Ali-Firat wrote:
>
> Hi Akka Team,
>
> I have an Akka app usin
See here:
https://github.com/akka/akka/blob/master/akka-remote/src/main/resources/reference.conf#L83
You can bind the exceptions you use to the built in akka-misc serializer.
If you are interested in how it's implemented look at
https://github.com/akka/akka/blob/master/akka-remote/src/main/scala
unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://g
You can try and compare Balance, Partition and PartitionHub.
/Patrik
> On Sep 19, 2017, at 00:16, Jakub Liska wrote:
>
> Hey,
>
> having an operation that heavily utilizes CPU and RAM, nothing else (no IO),
> but it is a main bottleneck, then it never pays off using `stream.mapAsync`
> for it
ons 20 sep. 2017 kl. 02:05 skrev Joe Wong :
> Hi,
>
> We have a setup of an akka cluster with the following: seed node, a master
> node, and worker nodes. Workers will broadcast a request work message that
> the master node respond to. We deployed this setup in Google Kubernetes
> environment. It
Event adapter is the recommended way to add tags, to keep the logic in the
actor free from this event consuming aspect.
/Patrik
tis 19 sep. 2017 kl. 18:52 skrev :
> Is there a way to add tags (i.e. *akka.persistence.journal.Tagged*) to
> domain events and *StateChangeEvent* in a *PersistentFSM* a
If the names are StreamSupervisor- I think it can be that a new
Materializer is created for each request. I don’t know if that is done by
your application or by Akka Http. Does that ring any bells? Do you have any
creation of stream materializers in your code?
/Patrik
mån 25 sep. 2017 kl. 21:51 sk
Enrique is right.
Use the CoordinatedShutdown feature for leaving the cluster and shutdown
the ActorSystem. The JVM can continue running and you can start new
ActorSystem that joins the cluster again.
/Patrik
ons 27 sep. 2017 kl. 03:38 skrev Enrique Ell Pereira :
> Hi Chad,
>
> As far as I unde
Thanks for reporting. It’s a mistake, we will fix (monday latest). Until
then you find close to latest scaladoc at
https://doc.akka.io/api/akka/2.5.4/
/Patrik
fre 29 sep. 2017 kl. 19:58 skrev Sarah Gerweck :
> I was just working on some development and it appears that all the
> Scaladoc documenta
1 - 100 of 2005 matches
Mail list logo
