Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Petabridge.Cmd actor hierarchy prints different results each time. #4585

Closed
seunghalee91 opened this issue Oct 20, 2020 · 1 comment
Closed

Comments

@seunghalee91
Copy link

Environment

  • Windows 10 Pro
  • Akka.Remote v1.4.10
  • Akka.Cluster v1.4.10
  • Petabridge.Cmd.Cluster v0.8.0.0
  • Petabridge.Cmd.Common v0.8.0.0
  • Petabridge.Cmd.Host v0.8.0.0
  • Remotely deploy the actor using ClusterSingletonManager.

Question

  • Petabridge.Cmd actor hierarchy prints different results each time.

our service

image

actor hierarchy -d 8 1st run

image

  • Received unexpected ActorIdentity Warning message
[2020/10/19 18:02:34.084][   29][ WARN]akka.tcp://mls-cluster-system@127.0.0.1:9830/user/petabridge.cmd/192.168.100.70%3A9846/actor/handler/$i/$b[Petabridge.Cmd.Host.Default.Actor.ActorTracer] Received unexpected ActorIdentity: [Id=akka.tcp://mls-cluster-system@127.0.0.1:9834/remote/akka.tcp/mls-cluster-system@127.0.0.1:9830/user/ApiMasterActor/ClusterSingleton/TestClusterRole1HelloActor/c1, Subject=]

actor hierarchy -d 8 2nd run

image

  • Received unexpected ActorIdentity Warning message
[2020/10/19 18:02:35.355][    4][ WARN]akka.tcp://mls-cluster-system@127.0.0.1:9830/user/petabridge.cmd/192.168.100.70%3A9846/actor/handler/$j/$b[Petabridge.Cmd.Host.Default.Actor.ActorTracer] Received unexpected ActorIdentity: [Id=akka://mls-cluster-system/user/ApiMasterActor/ClusterSingleton/TestClusterRole2HelloActor, Subject=[akka.tcp://mls-cluster-system@127.0.0.1:8112/remote/akka.tcp/mls-cluster-system@127.0.0.1:9830/user/ApiMasterActor/ClusterSingleton/TestClusterRole2HelloActor/c1#1502144516]]
[2020/10/19 18:02:35.451][   27][ WARN]akka.tcp://mls-cluster-system@127.0.0.1:9830/user/petabridge.cmd/192.168.100.70%3A9846/actor/handler/$j/$b[Petabridge.Cmd.Host.Default.Actor.ActorTracer] Received unexpected ActorIdentity: [Id=akka://mls-cluster-system/user/ApiMasterActor/ClusterSingleton/TestClusterRole1HelloActor, Subject=[akka.tcp://mls-cluster-system@127.0.0.1:9834/remote/akka.tcp/mls-cluster-system@127.0.0.1:9830/user/ApiMasterActor/ClusterSingleton/TestClusterRole1HelloActor/c1#1449701576]]

Why is the output different every time the actor hierarchy command?

@Aaronontheweb
Copy link
Member

I should transfer this over to https://github.com/petabridge/petabridge.cmd-issues but it looks like Github will only let me transfer issues between repositories in the same organization. In the future if you have a Petabridge.Cmd question I'd recommend posting there.

The reasons why the results are in different orders each time is because the actor hierarchy scan is done recursively in parallel down in the actor hierarchy using wildcard ActorSelections and the completion order of those parallel tasks is arbitrary. We're able to guarantee that a parent doesn't complete its scan until its children have completed theirs and so on, all the way until we reach the specified level of depth. But we don't guarantee the completion order of siblings - i.e. the order in which two children of the /user actor complete their scans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants