Number of routees reported on Clustered Group routers doesn't reflect actual number of routees cluster-wide

[Aaronontheweb]

Issue was originally reported here: petabridge/akkadotnet-code-samples#31

I've been able to verify that this is a bug inside Group routers. Looks like the number of routees correlates to the number of different routees.paths, when it should be routees.paths count X number of nodes.

[rogeralsing]

What does the "ready" tag mean? it's not in the Done column on waffle and its not closed, so what does it mean?

[Aaronontheweb]

@rogeralsing I think it means that this issue is queued up to be part of the next major release. @skotzko would know better than I would.

[matthewma7]

@Aaronontheweb Could you provide some information on this issue? and possibly, I could try to fix this?

[Aaronontheweb]

@MatthewMa sure, someone just created a reproduction case for this: https://github.com/idursun/akka.cluster.test

I have two nodes with different roles, one of them being the seed node. I also have a consisten-hash-group, and when i ask for routees, I get one routee, which is expected. I start another instance of the worker node and ask for routees and i still get one routee.

Does that help clarify things?

[Aaronontheweb]

Possibly related to #1700

[matthewma7]

@Aaronontheweb Hi, I have stepped the code, I think I did see just one routee. But I am sorry that I think I don't know enough about Akka.NET to fix this issue.

[alexvaluyskiy]

All group routers bugs were fixed here #2094

[alexvaluyskiy]

Fixed #2103