Hi Roland,
I went through important discussion on querying
at https://groups.google.com/forum/#!msg/akka-user/SL5vEVW7aTo/KfqAXAmzol0J.
But it did not take me to any conclusion. Thanks for this conclusion post.
Journal will always have the history of events. Why one will query for
history of
Hi Roland,
thanks for the summary, I think that's the right direction.
In your summary, the only query command type pre-defined in
akka-persistence is QueryByPersistenceId. I'd find it useful to further
pre-define other query command types in akka-persistence to cover the
most common use
On Wednesday, August 27, 2014 5:34:02 PM UTC+2, rkuhn wrote:
There is another possibility (if needed):
system.dispatchers.registerConfigurator(name, ...)
Thanks for this hint. Looks interesting indeed. Unfortunately this seems to
be an akka 2.3.x feature and we are still using akka 2.2
Hello, I have this use case and I would be curious if Akka is good solution
for it and how to do it correctly. I tried just hello world in Akka..
We have application on single server with consumes event of users' events
from message queue; generates user analytics from them; saves user
I am wondering how one peer in Akka remoting can detect that the other peer
has been quaranteed, so that it can restart the actor system used for
remoting to clear the quarantine? Is there an API call for finding out that
Akka has quarantined a peer? Or does the application need to use say
For the records: with J9VM - 20130423_146146 the problem is resolved
On Tuesday, August 26, 2014 9:57:01 AM UTC+2, Carsten Saager wrote:
Is there a J9 1.6 version that is know to work - or is there a WebSphere
(7.x) patch that enables Akka to run there?
-Carsten
On Saturday, September 7,
Do you really need to create that dispatcher dynamically? You can create a
custom static one that has dynamic behavior, basically just calling
UserGroup... and PrivilegedAction. I mean, I don't really see why the
dispatcher itself must be created dynamically, only its behavior needs to
Hi,
I am putting my thoughts based on Storm topologies where spout and bolts
can be configured and data flow for the system can be created. When
building a huge system it gets really apparent that we shall have work flow
mechanism of components. One real advantage is that storm topology are
Cool, thanks for sharing! (we don’t have the means to try this out)
Regards,
Roland
26 aug 2014 kl. 20:56 skrev Carsten Saager csaa...@gmail.com:
For the records: with J9VM - 20130423_146146 the problem is resolved
On Tuesday, August 26, 2014 9:57:01 AM UTC+2, Carsten Saager wrote:
Is
Hi Mario,
On Wed, Aug 27, 2014 at 9:12 PM, Mario Camou mca...@tecnoguru.com wrote:
Hi Roland,
It's not happening...
If you do it through localhost it works fine, but in the case where the
client is on a different machine from the Akka server, it doesn't happen.
I've tried with kill -9
And the ticket is here: https://github.com/akka/akka/issues/15766
On Thu, Aug 28, 2014 at 11:01 AM, Akka Team akka.offic...@gmail.com wrote:
Hi Mario,
On Wed, Aug 27, 2014 at 9:12 PM, Mario Camou mca...@tecnoguru.com wrote:
Hi Roland,
It's not happening...
If you do it through
Hi Martin,
On Thursday, August 28, 2014 8:01:43 AM UTC+1, Martin Krasser wrote:
In your summary, the only query command type pre-defined in
akka-persistence is QueryByPersistenceId. I'd find it useful to further
pre-define other query command types in akka-persistence to cover the most
Hi Prakhyat,
We are creating one actor system for entire app. Correct me if I am wrong, the
default dispatcher by default uses a fork-join thread pool with at least 8
threads.
We need to support millions of requests from client. How to tune
dispatcher of actor system when using akka
Hi Andre,
Thanks.
For point [1] What do you mean by It is also a very good practice to use
separate dispatchers for various parts of the system.
I have not seen any app with separate dispatchers. Kindly share any article
which describes this and app over github would be help.
I have my app
Hi Mario,
re-reading the docs it does sound like the channel should be woken up if it has
either OP_READ or OP_WRITE registered. The latter only is registered when you
try to write something without success, but the former should always be
registered unless you suspended reading (or did not
27 aug 2014 kl. 19:27 skrev Ashley Aitken amait...@gmail.com:
On Wednesday, 27 August 2014 23:08:27 UTC+8, rkuhn wrote:
In theory if Client sends a command to A which in order to fulfill it will
need to send a command to B then A’s response to the Client will contain B’s
reply in some
On Wed, Aug 27, 2014 at 9:25 PM, Roland Kuhn goo...@rkuhn.info wrote:
Hi Mario,
re-reading the docs
http://docs.oracle.com/javase/8/docs/api/java/nio/channels/SelectionKey.html
it
does sound like the channel should be woken up if it has either OP_READ or
OP_WRITE registered. The latter
Hi Azad,
On Wed, Aug 27, 2014 at 6:18 PM, Azad Bolour azadbol...@bolour.com wrote:
I am wondering how one peer in Akka remoting can detect that the other
peer has been quaranteed, so that it can restart the actor system used for
remoting to clear the quarantine? Is there an API call for
Hi Martin and Alex,
the point you raise is a good one, I did not include it in my first email
because defining these common (and thereby de-facto required) queries is not a
simple task: we should not include something that most journals will opt out
of, and what we pick must be of general
Hi Glenn,
I was having a bit of a browse around the code for fun the other day with
regards to this part (i'm pretty new to Akka in general, so some of these
parts might be common knowledge/obvious, but bear with me)
- It seems most everything inside akka is communicated with messages
Hi,
One more follow up question.
When using the setting advised by the documentation for this scenario
(http://doc.akka.io/docs/akka/snapshot/java/logging.html#SLF4J) the only
real gap from what I need is that with akka.logLevel set to DEBUG and with
the SLF4J binding configured to INFO,
Hi to all!
I have found this article
(http://techblog.net-a-porter.com/2013/12/ask-tell-and-per-request-actors/)
that is exactly my application in ask pattern.
Now, I trying to change my code in tell pattern, but I have a little
problem to management timeout.
My scenario:
- SystemActor (ask
Hi Andre,
Thanks. I looked into the post.
If we use multiple dispatchers and corresponding thread pools. How these
dispatchers will share cores in one machine.
Consider 3 dispatchers with 8 threads each on a dual core machine.
-Prakhyat M M
On Thursday, 28 August 2014 15:17:42 UTC+5:30,
On 28.08.14 12:00, Roland Kuhn wrote:
Hi Martin and Alex,
the point you raise is a good one, I did not include it in my first
email because defining these common (and thereby de-facto required)
queries is not a simple task: we should not include something that
most journals will opt out of,
I am unable to understand, How for business specific querying event stream
will function?
Journal will always have the history of events. Why one will query for
history of events? Most of the queries will require current state.
I linked a video in this thread that covers some such reasons
On
There's also the Remote Events section
of http://doc.akka.io/docs/akka/2.3.4/scala/remoting.html; I subscribe
to akka.remote.QuarantinedEvent events on the remoting ActorSystem.
On Thursday, August 28, 2014 5:50:36 AM UTC-4, Akka Team wrote:
Hi Azad,
On Wed, Aug 27, 2014 at 6:18 PM, Azad
Hi Roland, Endre and the rest :),
Here is an excerpted/simplified version of what we're doing (hopefully I
didn't mess things up too badly during sanitization):
class ConnectionListener(endpoint: InetSocketAddress) extends Actor with
ActorLogging {
import akka.io.{ IO, Tcp }
implicit val
I am trying to use the typesafe console with the atmos sbt plugin. I find
building the system difficult because I get Akka version not supported by
Typesafe Console. On a test project I was able to get past this by down
grading my scala and akka versions. This won't work on my current project.
Hi Roland,
On Thursday, August 28, 2014 11:00:17 AM UTC+1, rkuhn wrote:
Concerning types I assume that there is an implicit expectation that they
work like types in Java: when I persist a ShoppingCartCreated event I want
to see it in the stream for all ShoppingCartEvents. This means that the
Hi Roland,
great conclusion, with everything said till now in mind. I'd like to
mention a view points and like to hear if this matches your thoughts:
The QueryByTypeDeterministic(type, from, to) mentioned by Martin matches
with the way I've been using DDD+CQRS for last 2 years.
Meaning that
Thank you Endre and Steven for your responses.
A follow-up question. Do we have to set up remote death watch or subscribe
to the QuarantinedEvent in both peers? Or do we get the terminated message
and the quarantined event on one side no matter which side has quarantined
the other? It would be
Hi Roland,
It's a good summary. As far as I can see it looks very complete and allows
for a lot of flexibility between scalability and ease of use.
I will add that I am interested to see Martin's causal consistency with
zero application-specific hints or code (unless its just obvious previous
Hey Endre,
(Also CC akka-dev as I realised this type of low level stuff probably fits
in a lot better there..)
On Thursday, 28 August 2014 20:08:09 UTC+10, Akka Team wrote:
Hi Glenn,
I was having a bit of a browse around the code for fun the other day with
regards to this part (i'm
A few things.
First, while it is common that a projection is interested in only events
from a type of producer (aggregate/actor/etc) it's also quite common they
need to listen from many types.
I believe that it is quite important to have these API case classes
standardized as much as is
Thank you Roland and team for listening and sharing your ideas and plans.
As I have said, I think there are three different but related areas of
functionality being discussed here: 1) Actor Persistence, 2)
Publish-Subcribe (to Topics), and 3) Full CQRS support.
Conceptually, for CQRS (3), I
35 matches
Mail list logo
