4 mar 2015 kl. 16:10 skrev Brice Figureau brice...@daysofwonder.com:
On Tue, 2015-03-03 at 12:16 +0100, Patrik Nordwall wrote:
On Tue, Mar 3, 2015 at 11:37 AM, Björn Antonsson
bjorn.antons...@typesafe.com wrote:
Hi Brice.
I just noticed the other discussion. You are
3 mar 2015 kl. 11:45 skrev Anders Båtstrand ander...@gmail.com:
Thank you very much, that explain my issue!
I am still not sure if WriteMessageSuccessful can arrive after the actor is
stopped. I can find no reference to it in the docs...
I will find out after running code with
Hello,
I am using Akka Cluster Sharding because I have many stateful actors that
together don't fit on one machine.
Additionally I am also using Akka Persistence (with Cassandra journal) for
the snapshot mechanism (to recreate state).
For storing the events I would like to use a user defined
Thanks a lot Michael for getting to the bottom of this.
B/
On 4 March 2015 at 22:04:32, 'Michael Overmeyer' via Akka User List
(akka-user@googlegroups.com) wrote:
I've dug into this some more. It turns out that akka-persistence is using
leveldb correctly, but leveldb has issues when you store
Hi Tim!
I can’t reproduce what you mention, which exact jar are we talking about?
I downloaded the source jar from:
http://search.maven.org/#artifactdetails%7Ccom.typesafe.akka%7Cakka-stream-experimental_2.11%7C1.0-M4%7Cjar
and it does seem to contain valid javadoc, or am I missing something?
//
I wanted to open a quick discussion on this before reporting a bug; is
there a reason (other than nobody has implemented it yet) why the Scaladocs
are not included in the akka-stream-experimental release? Any sense of the
complexity / what is needed to change that?
I'd like to get the docs
I've dug into this some more. It turns out that akka-persistence is using
leveldb correctly, but leveldb has issues when you store large values.
See this https://github.com/akka/akka/issues/13962and this
https://groups.google.com/forum/#!msg/leveldb/yL6h1mAOc20/vLU64RylIdMJ
for the full
I'm writing a task dispatching system for scientific data collection on
timesharing clusters. There is a specific API for submission of tasks and a
few implementations one of which does the data collection locally, another
to a MySQL Server, and the one I am working on currently an Akka based
Is there a maximum value set for nr-of-instances?
When I set it to 300, it works fine.
When I set it to 400, I see [WARN]
[xxx-akka.remote.default-remote-dispatcher-5] [Remoting] Association to
[akka.tcp://xxx@127.0.0.1:2552] with unknown UID is irrecoverably failed.
Address cannot be
Hi,
I am trying to get the hang of Akka Streams and have been struggling last
night with some of the examples in the Streams documentation because of
this api change. It would be great if the documentation could be updated so
other newbies don't get stuck like me.
Thanks for your reply. It
Hi Joost,
On Wed, Mar 4, 2015 at 8:26 AM, Joost den Boer jdb...@diversit.eu wrote:
Hi,
I am trying to get the hang of Akka Streams and have been struggling last
night with some of the examples in the Streams documentation because of
this api change. It would be great if the documentation
Hi Jim,
The job of moving streams to 2.4 will be started as soon at it has reached a
stable state on 2.3. There is no ETA for a streams port to 2.4, but rest
assured that it will be available before 2.4 is released.
B/
On 3 March 2015 at 19:48:07, Jim Hazen (jimhazen2...@gmail.com) wrote:
Is
To add some anecdotal explanation as well, this was the thought process:
source.runWith(sink) is used mostly for the purpose of getting something out of
that sink, so the materialized value will default to the right hand side of the
operator.
An alternative formulation is source.to(sink).run(),
Hi,
That is by design. Calling onError inside the ActorPublisher will Terminate the
stream with the failure (it's in the doc for the method). If you on the other
hand throw an exception during your processing I assume that the
SupervisionDecider will decide what to do.
B/
On 3 March 2015 at
Hi all,
I have an actor which in the constructor creates a router actor which
creates several workers.
Also, in that actor, it creates an actor do so some separate stuff, so the
structure is like:
actor router -- a bunch of workers
listener
As said, router and listener are
On Tue, 2015-03-03 at 12:16 +0100, Patrik Nordwall wrote:
On Tue, Mar 3, 2015 at 11:37 AM, Björn Antonsson
bjorn.antons...@typesafe.com wrote:
Hi Brice.
I just noticed the other discussion. You are right, the Region
that is persisted contains an
16 matches
Mail list logo
