dependabot[bot] on nuget
Bump PublicApiGenerator from 9.… (compare)
dependabot[bot] on nuget
Bump FluentAssertions from 5.10… (compare)
dependabot[bot] on nuget
Bump Fsharp.Core from 6.0.1 to … (compare)
dependabot[bot] on nuget
Bump NUnit from 3.7.1 to 3.13.3… (compare)
dependabot[bot] on nuget
Bump System.Configuration.Confi… (compare)
dependabot[bot] on nuget
Bump System.Collections.Immutab… (compare)
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
}
}