Two possibilities:
1. Go out-of-band and drop down to Http using, say, Netty. Flink does this
(it uses Akka remoting for command-and-control but transmits data using
Netty).
2. Stick the files on a blob store like S3 and just send messages telling
the other actor a file is available (or whatever the relevant event is).
Note that S3's consistency guarantees make this tricky as you can't assume
the remote actor will be able to read a file you just wrote so you'll need
retries and proper failure handling.
On Thursday, April 27, 2017 at 2:46:25 AM UTC-6, Sumanta Dutta wrote:
>
> Hi, we generally use ask pattern to handle request-response between client
> and Akka Cluster. The client waits on the Future. We have a need where the
> response size (~150MB) is too large to fit in one message even after
> increasing message-frame-size to -
>
> maximum-payload-bytes = 50000000 bytes
> netty.tcp {
> message-frame-size = 50000000b
> send-buffer-size = 50000000b
> receive-buffer-size = 50000000b
> maximum-frame-size = 50000000b
> }
>
> We don't like keep increasing the above limits. So one possibility is to
> break the response in small chunks, but then how to handle on the Future
> side using the ask pattern. The other possibility may be to use GraphStage
> between Actors to stream the response back. Is that a viable solution? Is
> there any example out there?
>
> Thanks,
> Sumanta
>
--
>>>>>>>>>> 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.
