Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
  • 18:11
    Aaronontheweb commented #4742
  • 17:03
    Horusiath commented #4742
  • 16:10

    Aaronontheweb on dev

    Update cluster-overview.md (#47… (compare)

  • 16:10
    Aaronontheweb closed #4743
  • 16:10
    Aaronontheweb labeled #4743
  • 15:55
    to11mtm commented #4742
  • 14:16
    brah-mcdude opened #4743
  • 06:11
    Horusiath commented #4742
  • 06:07
    Horusiath commented #4742
  • Jan 23 19:44
    to11mtm synchronize #4742
  • Jan 23 19:22
    to11mtm commented #4742
  • Jan 23 18:29
    to11mtm commented #4737
  • Jan 23 18:16
    to11mtm commented #4736
  • Jan 23 18:11
    to11mtm edited #4736
  • Jan 23 18:00
    to11mtm review_requested #4742
  • Jan 23 17:59
    to11mtm edited #4742
  • Jan 23 17:58
    to11mtm review_requested #4742
  • Jan 23 17:52
    to11mtm opened #4742
  • Jan 23 03:10
    seungyongshim edited #4733
  • Jan 22 18:02
    IgorFedchenko closed #4738
Aaron Stannard
@AnchishkinAlex are you remotely deploying those actors?
if not, then none of this stuff matters - both actors are started independently
and neither needs to know about each other's constructor arguments
they just need to acquire a remote actor reference to each other
which you can via an ActorSelection initially
Ok, we tried to use ActorSelection but it needs hardcode address of actor.
Is it possible to get address of actor from HOCON?
Aaron Stannard
yep, you can create a custom HOCON field
to store the address a remote node
I do this inside the client-server app from our Akka.NET trainings
let me see if I can grab it...
              handshake-timeout = 4.0s #max time to complete the handshake timeout process
              verify-timeout = 1.0s #max time to authentication an end-user locally on the server
              verify-chat = on
             server = "akka.tcp://akkatime@"

          akka {
the akkatime section is custom
and I have a akkatime.server property that the client reads from configuration in order to figure out how to contact the server
var actorSystem = ActorSystemRefs.AkkaTimeSystem = ActorSystem.Create("akkatime");
            var serverAddress = ActorSystemRefs.ServerAddress = Address.Parse(actorSystem.Settings.Config.GetString("akkatime.server"));
            var serverStatus =ActorSystemRefs.ServerConnectivityActor =
                    Props.Create(() => new ServerConnectivityStatusActor((Address)serverAddress.Clone(), ServerConnectivityStatus.Disconnected)),
which I then read in here when I'm starting my ActorSystem
and that serverAddress gets passed to an actor that uses an ActorSelection to contact another actor on the server
Thank you. Could you provide link to this example? I'll explain it
Aaron Stannard
wish I could, but it's part of the training materials we distribute to our customers
that being said, we do have all of these ones
the WebCrawler one for Akka.Cluster is probably the most relevant there
Thanks! I saw Akka.NET Bootcamp, Chat Server Example but not this samples :smile:
Aaron Stannard
you're welcome!
And I know about your post "When I should use Actor Selection?". Is this situation relevant, isn't it?
Aaron Stannard
yes it is
generally, IActorRef is going to be both more performant and flexible at run-time
since it has the benefit of location transparency and doesn't need to be "resolved"
but ActorSelection is ideal in situations where you don't have a reference to an actor yet but still need to contact it
and you know roughly where it is in the hierarchy
most people build their actor hierarchies top-down
where the top level actors filter messages down to their children and so forth
so by convention, most developers treat their top level actors like "public APIs"
therefore, it's usually safe to select those and trust that your message will eventually be routed to the correct concrete actor who will actually do the processing
and that actor will send you a reply back directly
you can also do some cool stuff with wildcard actor selections
i.e. akka.tcp://mysys@*/myGrandChild
you can dynamically select all of the grand children of myParent named myGrandChild without knowing what the parent's name is
I used that to build our actor hierarchy visualizer in Petabridge.Cmd: https://cmd.petabridge.com/articles/commands/actor-commands.html#actor-hierarchy
it's interesting
So well! We will try Actor Selection for this moment. Thanks again! All the best! :smile:
Can some please explain the philosophy behind this Cluster Sharding shenanigans.
Aaron Stannard
@vicosoft4real Cluster.Sharding tries to guarantee that there is exactly one copy of a given entity inside your cluster at any given time
where each entity is represented as its own actor
it has tooling in place to do things such as redistribute entities when the cluster changes
buffer messages being sent to a given entity while it's being moved
and a placement algorithm for figuring out where it should spawn new ones
each entity should, ideally, persist its state somewhere
sounds good