Hi Martynas,
I am trying to do a data shuffle between two layers.
On the upstream, there are a layer with multiple actors.
On the downstream, there are another layer with multiple actors.
Each upstream actor will distribute the message flowed by it to all
downstream actors, maybe groupped the
The documentation
at http://doc.akka.io/docs/akka/snapshot/scala/cluster-usage.html doesn't
state that the PoisonPill performs differently than the behaviour listed
here
http://doc.akka.io/docs/akka/snapshot/scala/routing.html#note-router-terminated-children-scala,
so I assumed if I used a
Hi Martynas Mickevičius,
thank you, this fixed the connection problem with the hostname that I
reported in the other thread! :-)
Pierre
Also I just noticed an error in your configuration. Instead:
remote {
enabled-transports = [akka.remote.netty.tcp]
hostname = Vortex
How to run akka stream distributedly in a cluster?
Suppose a Flow DSL will be translated to 100 actors. How to configure these
actor in start in different machine of the cluster?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
That’s currently not supported.
Streams are a very fresh module, and we’re still working to get the in-jvm
semantics and APIs *right* before we go distributed.
--
Konrad 'ktoso' Malawski
hAkker @ typesafe
http://akka.io
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Hi
I found a small bug in the implementation of the ActorProducer.
I created an Actor (which has the ActorProducer implemented)
I did not use the actor (I just created it)
When now the system is shutdown the following exception occurs
*Exception:*
java.lang.NullPointerException: null
Thanks,
I come from bigdata background.
In my opinion, the Flow DSL is not expressive for many cases, like data
shuffle. Have you considered using DSL like the one used in cascading, or
spark, or storm trident?
How can I help in this process?
Sean
On Monday, July 14, 2014 4:26:58 PM UTC+8,
HI Sean,
I come from bigdata background.
In my opinion, the Flow DSL is not expressive for many cases, like data
shuffle. Have you considered using DSL like the one used in cascading, or
spark, or storm trident?
The primary goal for streams is to provide a unified way to handle
As Endre already highlighted, we have a different focus than the
specialised-for-big-data frameworks.
Our focus is to get the back-pressure semantics and common API among library
implementors right (the reactive streams API).
There’s a lot of discussions around these still happening at
Thank you both for your reply.
I believe there lacks some combinators, I will comment later after I check
the github todo list.
On Monday, July 14, 2014 4:55:59 PM UTC+8, Konrad Malawski wrote:
As Endre already highlighted, we have a different focus than the
specialised-for-big-data
Hello Jeff,
Basically I want to pile a bunch of messages into this mailbox and have the
actor process them when it can with a producer timeout restriction. I
know this is related to the Reactive Stream stuff, but I'm interested in
something near term and deciding if I should implement a
Hi All,
I want to use the typed actor's router. But I only see the untyped actor
router code.
Do you have the java code for creating typed actor router? Thanks
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
I added the issue https://github.com/akka/akka/issues/15535
Am Montag, 14. Juli 2014 11:24:28 UTC+2 schrieb Konrad Malawski:
Thanks for reporting, Wolfgang!
Looks like a bug indeed, would you mind creating an issue with these
details on our issue tracker?
Thanks for reporting Wolfgang!
We’ll look into this.
On 14 July 2014 at 12:47:42, Wolfgang F. (wolfgang.fri...@hotmail.com) wrote:
I added the issue https://github.com/akka/akka/issues/15535
Am Montag, 14. Juli 2014 11:24:28 UTC+2 schrieb Konrad Malawski:
Thanks for reporting, Wolfgang!
Looks
Hello there,
Since TypedActors are implemented as plain message sends (the message
representing the proxy method calls is called MethodCall), you can simply
do an untyped router, and then add a typed proxy before it:
TypedActor Router must {
work in {
val t1 = newFooBar
val t2 =
3 pigdog
On Mon, Jul 14, 2014 at 1:24 PM, Konrad Malawski
konrad.malaw...@typesafe.com wrote:
Hello there,
Since TypedActors are implemented as plain message sends (the message
representing the proxy method calls is called MethodCall), you can simply
do an untyped router, and then add a
You know it's Victor's code if there's pigdogs inside :-)
PS: I'm not sure if this a pattern popular enough to embrace and add it to
the docs... Opinions?
On Mon, Jul 14, 2014 at 1:26 PM, √iktor Ҡlang viktor.kl...@gmail.com
wrote:
3 pigdog
On Mon, Jul 14, 2014 at 1:24 PM, Konrad Malawski
Viktor's* - I keep mistyping your name recently, don't know why. Sorry,
Viktor. ;-)
On Mon, Jul 14, 2014 at 1:26 PM, Konrad Malawski kt...@typesafe.com wrote:
You know it's Victor's code if there's pigdogs inside :-)
PS: I'm not sure if this a pattern popular enough to embrace and add it to
It's alright Kônräd :)
On Mon, Jul 14, 2014 at 1:29 PM, Konrad Malawski kt...@typesafe.com wrote:
Viktor's* - I keep mistyping your name recently, don't know why. Sorry,
Viktor. ;-)
On Mon, Jul 14, 2014 at 1:26 PM, Konrad Malawski kt...@typesafe.com
wrote:
You know it's Victor's code if
Hello Javier,
It's a bit hard to answer on event design questions when we discuss
Entity and Event :-)
But in general these events should have some meaning, not only
AttributeUpdated - as in BughtItem, ShippedThingy, ConfirmedPayment.
Play around with the granularity of your events, maybe you're
On Mon, Jul 14, 2014 at 1:26 PM, Konrad Malawski kt...@typesafe.com wrote:
You know it's Victor's code if there's pigdogs inside :-)
PS: I'm not sure if this a pattern popular enough to embrace and add it to
the docs... Opinions?
I think it is useful enough.
On Mon, Jul 14, 2014 at
Definitely we're not choosing the perfect granularity.
I'll try to focus in meaningfull methods instead of isolated attribute
changes.
Thanks for your time, Konrad :-)
El lunes, 14 de julio de 2014 13:51:35 UTC+2, Konrad Malawski escribió:
Hello Javier,
It's a bit hard to answer on event
Hello Pavel,
It seems to me that you’re overdoing a lot inside that implementation.
I don’t really see what gain your own deliveryIds is meant to provide.
Let’s take a step back and look at the semantics of deliver and
confirmDelivery *during playback*.
During normal operation I think it’s clear
This thread motivated me to improve the documentation on these methods a
bit, progress can be tracked in this
issue: https://github.com/akka/akka/issues/15538
-- k
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
0down vote*favorite*
http://stackoverflow.com/questions/24736060/javafx-akka-dispatcher-leaks#
I have created an executor:
public class GUIExecutorService extends AbstractExecutorService {
@Overridepublic void shutdown() {
}
@Overridepublic ListRunnable shutdownNow() {
return new
There's now a first release of the Kafka journal. Details at
https://github.com/krasserm/akka-persistence-kafka
Am Sonntag, 13. Juli 2014 16:19:55 UTC+2 schrieb Martin Krasser:
On 13.07.14 16:03, Richard Rodseth wrote:
Thanks for the detailed reply. I might have been forgetting that
On 14.07.14 16:46, Jonas Bonér wrote:
Great work Martin.
Thanks!
On Mon, Jul 14, 2014 at 4:36 PM, Martin Krasser
krass...@googlemail.com mailto:krass...@googlemail.com wrote:
There's now a first release of the Kafka journal. Details at
Fantastic!
Great work, Martin. Keep it coming!
Heiko
On 14 Jul 2014, at 16:36, Martin Krasser krass...@googlemail.com wrote:
There's now a first release of the Kafka journal. Details at
https://github.com/krasserm/akka-persistence-kafka
Am Sonntag, 13. Juli 2014 16:19:55 UTC+2 schrieb
Thanks Heiko, really hope to get some user feedback ...
On 14.07.14 17:04, Heiko Seeberger wrote:
Fantastic!
Great work, Martin. Keep it coming!
Heiko
On 14 Jul 2014, at 16:36, Martin Krasser krass...@googlemail.com
mailto:krass...@googlemail.com wrote:
There's now a first release of the
A couple of quick questions about passivate and PersistentActors:
Can other actors still send messages to persistent actors that have been
passivated?
Will these messages cause the persistent actor to be reactivated?
I am asking about this in single node and clustered context.
I saw
Hi,
We have MonitoringMaster actor system and N Metrics actor systems.
They are deployed in AWS, and to make it working we are substituting
public-ip in runtime.
Akka version: 2.2.4 (can't upgrade to 2.3.x due protobuf dependency)
Config file:
akka {
loglevel = INFO
log-config-on-start =
How to detach a custom dispatcher ?
--
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
Pull request here: https://github.com/akka/akka/pull/15540
On Mon, Jul 14, 2014 at 2:33 PM, Jonas Bonér jo...@jonasboner.com wrote:
On Mon, Jul 14, 2014 at 1:26 PM, Konrad Malawski kt...@typesafe.com
wrote:
You know it's Victor's code if there's pigdogs inside :-)
PS: I'm not sure if
Could you give some more context about what you are trying to achieve?
On Mon, Jul 14, 2014 at 7:22 PM, Oleksandr Ryabuha ale...@gmail.com wrote:
How to detach a custom dispatcher ?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
I have created an executor:
public class GUIExecutorService extends AbstractExecutorService {
@Overridepublic void shutdown() {
}
@Overridepublic ListRunnable shutdownNow() {
return new ArrayList();}
@Overridepublic boolean isShutdown() {
return false;}
@Overridepublic boolean
When remote actor's JVM is killed via ^C, watchers (on different JVMs) do
not get Terminated Messages.
They get:
Association with remote system [akka.tcp://blah@127.0.0.1:2553] has
failed, address is now gated for [5000] ms. Reason is: [Disassociated].
I know that they get Terminated messages
I forgot: Actor B in this case runs akka 2.3.0
Actor A is within a play system that runs play 2.3.1, and is running an
akka 2.3.0 version of remote(libraryDependencies += com.typesafe.akka %%
akka-remote % 2.3.0)
--
Read the docs: http://akka.io/docs/
Check the FAQ:
37 matches
Mail list logo
