sealed trait State
import scala.concurrent.duration._
import akka.actor._
sealed trait Data
case object Initial extends State
case object Waiting extends State
case object Empty extends Data
class FSMActor extends LoggingFSM[State, Data] {
startWith(Initial, Empty)
I run a very small, 3 node cluster on EC2 and I observerve constant
disassociacions.
Heartbeats are exchanged, nothing is lost:
05:52:06.702 [sgActors-akka.actor.default-dispatcher-62] DEBUG
a.c.ClusterHeartbeatSender: Cluster Node
[akka.tcp://sgact...@app1.sgrouples.com:2552] - Heartbeat to
Hi,
I want to use ClusterSingletonManager, but it is not possible to set
supervision strategy for its child (like with Router). What should I do?
- copy ClusterSingletonManager implementation and add parameter
- override ClusterSingletonManager (factory methods from companion
object
The same situation happens also if both nodes are on the same node, so
probably it's not a network issue, but rather some problem in the code,
maybe some silent exception that causes EndpointWriter to disassociate, but
there is no trace of it in the logs.
--
Read the docs:
If I add more nodes - they are disconnected at almost exactly the same time
11:24:42.232 [sgActors-akka.actor.default-dispatcher-62] WARN
a.r.ReliableDeliverySupervisor: Association with remote system
[akka.tcp://sgActors@10.89.144.8:2555] has failed, address is now gated for
[0] ms. Reason
I got that the other part is breaking connection
2015-04-03 12:07:53,806 INFO akka.actor.LocalActorRef
akka://sgActors/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FsgActors%4010.90.23.151%3A39036-1
- Message [akka.remote.transport.Association
Handle$Disassociated] from
You'll need to either use a test framework which can deal with async tests
or you'll have to wait for the result and perform the assertion at the end
of each test.
--
Cheers,
√
On 3 Apr 2015 00:21, Allen Nie aiming...@gmail.com wrote:
Thank you Viktor!! I tried to switch from test to App, and
Hi folex,
thanks for reporting.
Around that time this commit was merged into FSM
https://github.com/akka/akka/commit/2c88bb116903b42decb9d8063dc410325a9b9d29
which indeed changes semantics of `stay()` slightly (see documentation). It
changed when state transitions are triggered (the events).
I
When thinking about it again it, I think we need to document properly how
timeouts when both stateTimeout and forMax is used,
and then make it so. Currently it’s not very well defined.
In your case, when you change stateTimeouts I’d personally not use
stateTimeout but always forMax(),
which ends
Hi Tim,
Correct, when running from sbt you should fork, as documented here:
http://doc.akka.io/docs/akka/snapshot/scala/persistence.html#Testing
I guess you are refering to:
http://stackoverflow.com/questions/19425613/unsatisfiedlinkerror-with-native-library-under-sbt
As long as you have the
3 apr 2015 kl. 17:34 skrev Akka Team akka.offic...@gmail.com:
Hello Olle,
Are there any way of not having all cluster-singleton actors running on the
same node ( the leader node of the cluster ) in case that a service needs to
be migrated to another node because of other reasons than
Hi Magnus,
But is this is a bug or expected behaviour?
Yes, it is expected behavious.
ActorPublisher / Subscriber / Processor are not meant to be sent around
over the network, thus they are not serializable.
We'd like to work on distributing streams in an akka cluster, but it's not
a 1.0 goal
Hi Mark,
since you are building a concurrent system based on messaging (Actors),
you can never safely know that a queue is really and finally empty *just* by
looking at the queue.
Reason: there might be a message in flight to this Actor, and the second
after you've inspected the queue to be empty
Hi,
I'm trying to figure out how one would model a user system (register,
login, update) with Akka persistence.
As I am quite new to as well Actors as well as Event Sourcing and CQRS i'm
going forward and backwards on ideas.
Right now I would basically see one solutions:
Authenticator Actor
Thank you for the answers. I have been looking into Kamon, which provides
metrics for this. It seems to work, but I'm uncertain of the implications
of the AspectJ weaving within the Actor system. Using VisualVM etc
unfortunately does not provide any insights, since thread pool metrics are
not
The easiest is to just build the project you need, as in `project
akka-actor; publishLocal`.
You can disable generating PDFs by setting: enableOutput in
generatePdf := false
in the build (or REPL via `set ...`)
We're using the sbt-site plugin to do this:
Hi Syd,
I agree the previous suggestion in this thread.
It's best to keep these things as user land messages - so when you publish
these messages when you're done publishing send an NoMoreWork,
when an Actor processes this message it can safely shut itself down.
If you need to shutdown the actor
Hello Olle,
Are there any way of not having all cluster-singleton actors running on the
same node ( the leader node of the cluster ) in case that a service needs
to be migrated to another node because of other reasons than a node is down
( out of disk space or something like that ).
It does
18 matches
Mail list logo
