[akka-user][deprecated] Stream loops
Hello,
I have seen threads on this forum where Akka team recommends trying to
avoid stream loops ("they are tricky"). I have a use case where steams with
loops could be a solution to otherwise difficult problem.
the payload of the stream is a list of automatically formed case classes
from an input file, plus a wrapper case class with . at a given stage:
1. pop the next case class in the list and match {
case A --> do some stuff, pull some info out of A, set a field (i.e.
create new case object to preserve immutabilty) of the wrapper case class =
to a field of the A class, loop back to this stage with the list of case
classes not including A
case B --> do other stuff, add info from B to wrapper case class, loop
back to this stage with list of case classes not including B
.
.
.
} . // and the point here is there could be 0 to many As, Bs, Cs, etc
case F --> send to AthroughEExhaustedState
2. AthroughEExhaustedState might have its own similar rules
is this insanity? or am I missing a much better solution?
--
*
** New discussion forum: https://discuss.akka.io/ replacing akka-user
google-group soon.
** This group will soon be put into read-only mode, and replaced by
discuss.akka.io
** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced
*
>>
>> Read the docs: http://akka.io/docs/
>> 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 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 this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
[akka-user][deprecated] Artery TCP ready for production?
Hi all, 2.5.10 akka release notes state "However, since it’s a new implementation the TCP/TLS transport is not ready for usage in production yet, but please test it and report any issues." and we have the same warning on remoting docs page. What's the actual status on this? Anyone using it for extended period of time? We've tried switching from netty to artery tcp (akka 2.5.13) and testing seemed to be ok, on production we are seeing some odd behaviour: - steady increase of memory consumption (have to dig deeper to take some dumps, but memory graphs indicate this across all cluster nodes), it also seems that memory usage increases in other nodes if one node gets terminated unexpectedly (e.g. killed by kubernetes because of OOM) - nodes randomly failing to join cluster after restart (we use autodown) >From the logs when joining fails there are a lot of messages with "akka.stream.Materializer - [outbound connection to [akka://live@10.48.3.188:2550], message stream] Upstream failed, cause: Association$OutboundStreamStopQuarantinedSignal$:" -- * ** New discussion forum: https://discuss.akka.io/ replacing akka-user google-group soon. ** This group will soon be put into read-only mode, and replaced by discuss.akka.io ** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced * >> >> Read the docs: http://akka.io/docs/ >> 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 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 this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
