Hi Shiva,
Spark will likely be too high latency for you. Practical minimal batch
size is a couple seconds.
Think of Akka as a best fit for if you want to deploy individual apps each
reading from some set of fixed Kafka partitions. Each one could then write
to HDFS. However you would need
Hi guys,
I have a host which is Akka 2.3.15 (yes I know that's ancient, but can't
help it for now) running Akka cluster.
Now I have a remote client connecting to it, using
system.actorSelection(.).
The client can connect from the host that the server is running on, no
problem -- if I use
Never mind, found the solution to this:
val node1testActor = system.actorSelection(node(first) / "system" /
"testActor1")
node1testActor ! results
On Wednesday, October 12, 2016 at 3:53:12 PM UTC-7, Evan Chan wrote:
>
> Hi Hakkers,
>
> So I'm using MultiNo
Hi Hakkers,
So I'm using MultiNodeSpec to test some Akka Cluster functionality.
Basically I have a consistent hashing router which hashes based on each
node's Akka system address, and thus the port number is essentially random.
Thus from run to run of the test I cannot predict how many
do not support dynamic merging in the sense of allowing
streams to come and go. I do agree that this is a must-have, though.
Regards,
Roland
13 feb 2015 kl. 08:29 skrev Evan Chan vel...@gmail.com:
Dear friends,
I've read and grok the back-pressure story around Akka streams, which
Dear friends,
I've read and grok the back-pressure story around Akka streams, which is
pull-based. I have also seen examples of this with fixed topologies that
tend to be relatively linear or are fan-out: for example, a coordinator
farming work out to worker nodes. For these examples, I can
in the Graph. The only solution that I can
think of at the moment is to have a PropsSource and a PropsSink that
materialize into actors, and then you connect them on the side by sending
normal actor messages.
B/
On 27 January 2015 at 17:08:59, Evan Chan (vel...@gmail.com) wrote:
I got feedback
Ping anybody?
On Thursday, January 15, 2015 at 4:59:19 PM UTC-8, Evan Chan wrote:
Hey folks,
I would like to implement an at-least-once ingestion pipeline, say from a
source like Kafka, to a datastore, using Akka streams.
The method of at-least-once is that each incoming message has
Hey folks,
I would like to implement an at-least-once ingestion pipeline, say from a
source like Kafka, to a datastore, using Akka streams.
The method of at-least-once is that each incoming message has an increasing
numeric offset, and the idea is that successful writes into the datastore
:02 AM UTC-6, Evan Chan wrote:
The discussion was very long but didn't produce any conclusions.
One possible piece to start with is to make the Akka discovery of other
nodes pluggable (whereas the great threshold detection and up/down logic
would remain); for example, maybe the other nodes can
Hi Carsten,
On Wednesday, June 11, 2014 2:35:27 AM UTC-7, Carsten Saathoff wrote:
And there is another aspect. Especially for larger projects microservices
are great to enforce a share nothing philosophy. Using akka
serialization, I either have to share the messages or use protobuf + code
the introduction of modules) instead of the rather
irrelevant notion of “size” .
2 jun 2014 kl. 17:51 skrev Evan Chan vel...@gmail.com:
Hey guys,
I would like to run an idea by the fine Akka community - which is to
discuss what it would take to turn Akka into a platform for building
Hi Roland,
Thanks for thoughts...
On Thursday, June 5, 2014 6:57:38 AM UTC-7, rkuhn wrote:
*Data Flow Topology*
- Akka is pretty good at this already, supporting many types of data
flow. The only concern I see is that you have to define the flow via the
like of routers and such, which
a losing proposition.
Can you try to clarify what you are envisioning?
~thomas
On Monday, June 2, 2014 8:51:06 AM UTC-7, Evan Chan wrote:
Hey guys,
I would like to run an idea by the fine Akka community - which is to
discuss what it would take to turn Akka into a platform for building
Hey guys,
I would like to run an idea by the fine Akka community - which is to
discuss what it would take to turn Akka into a platform for building a
network of microservices: each one independently redeployable and easy to
change, yet through a common platform, take advantage of the
15 matches
Mail list logo
