Hi @Aaronontheweb
In your post here: https://petabridge.com/blog/intro-to-persistent-actors/ , you mentioned the following:
The PersistenceId and the SequenceNr, together, form the primary key. And the sequence number is a value that monotonically increases in-memory inside the persistent actor - so imagine if you have two actors with the same PersistenceId but different sequence numbers writing to the same store. It will be chaos and will inevitably error out - so that’s why it’s crucial that every PersistenceId be globally unique within your ActorSystem (at least for all actors writing to that store.)
I have a question regarding the "PersistenceId" in Akka.net in a cluster. Does it work like this or should I need a specifier per node ?
hey guys, I keep getting this error using actors in a cluster and sending messages:
[ERROR][10/15/2017 11:13:38][Thread 0010][remoting] Cannot find serializer with id [9]. The most probable reason is that the configuration entry 'akka.actor.serializers' is not in sync between the two systems.
my hocon config
akka {
actor {
provider =
\"Akka.Cluster.ClusterActorRefProvider, AkkA.Cluster\"
}
remote {
log-remote-lifecycle-events = DEBUG,
helios.tcp
{
hostname = \"localhost\",
port = 7000
}
}
cluster {
seed-nodes= [ \"akka.tcp://ClusterSystem@localhost:7000\" ]
}
serializers {
messagepack =
\"Akka.Serialization.MessagePack\"
}
serialization-bindings {
\"System.Object\" = messagepack
}
}
having
serializers
{
}
doesn't work
you have to have serializers {....
}
Hi all! I have a small problem with Akka.IO, very rarely I get this error: Resource temporarily unavailable
However, no event Tcp.Closed nor Tcp.PeerClosed is sent to neither of the connection handlers.
After a bit of debugging I was also able to see that my handlers are correctly registered (stored inside the ConnectionInfo).
The error is coming from this line TcpConnection.cs#L835:
[DEBUG][10/15/17 11:56:01 PM][Thread 0006][[akka://benchmark-a/system/IO-TCP/$a#359412270]] Closing connection due to IO error System.Net.Sockets.SocketException (0x80004005): Resource temporarily unavailable
at System.Net.Sockets.Socket.Send(IList`1 buffers)
at Akka.IO.TcpConnection.PendingBufferWrite.<DoWrite>g__WriteToChannel7_0(ByteString data, <>c__DisplayClass7_0& )
at Akka.IO.TcpConnection.PendingBufferWrite.DoWrite(ConnectionInfo info)
[DEBUG][10/15/17 11:56:01 PM][Thread 0003][[akka://benchmark-a/system/IO-TCP/$a/$a#757063873]] Closing connection due to IO error System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
[INFO][10/15/17 11:56:01 PM][Thread 0006][akka://benchmark-a/system/IO-TCP/$a] Message SocketReceived from akka://benchmark-a/deadLetters to akka://benchmark-a/system/IO-TCP/$a was not delivered. 1 dead letters encountered.Unfortunately, I was not able to create a reproducible example as it happens only from time to time during the launch of my benchmarks with BenchmarkDotNet.
