These are chat archives for akkadotnet/akka.net

2nd
Dec 2018
Chris
@chriskolenko
Dec 02 2018 00:32

Is there any gotcha's when using Cluster Discovery Consul + Routing?

Here is my deployment config:

            /other {
                router = broadcast-group
                routees.paths = ["/user/api"]
                virtual-nodes-factor = 8
                cluster {
                    enabled = on
                    max-nr-of-instances-per-node = 2
                    allow-local-routees = off
                    use-role = "other"
                }
            }

I have the other console application running with an actor ready for messages at /user/api

Here is the cluster config:

    cluster {
        roles = ["other"]
    }

Logs are showing that the nodes are up and running with the correct roles.

But the when telling /user/other a message it keeps deadlettering. Anyway to debug what's going on?

Oh... I'm having no issues with routing when I'm broadcasting to the same role + enabling allow-local-routees. But once scaling up I'm sure the external routees wouldn't work :(
Chris
@chriskolenko
Dec 02 2018 01:47
^^^^^^^^^ Nevermind.. Found my issue..
Was creating the ActorSystems with different names. Once I figured it out, started working like a charm. :D
AndreSteenbergen
@AndreSteenbergen
Dec 02 2018 16:20
Doe anyone knwo why this can occur in a cluster? I see a lot of these in my logs
[ERROR][12/2/18 4:18:21 PM][Thread 0007][remoting] SkipLastField called on an end-group tag, indicating that the corresponding start-group was missing
Cause: Google.Protobuf.InvalidProtocolBufferException: SkipLastField called on an end-group tag, indicating that the corresponding start-group was missing
Can my MsgPack serialization be the reason that message in protobuf is raised? All my own messages are serialized in MsgPack, but I can't find a lot googling this error.
Zied
@zimayel_gitlab
Dec 02 2018 18:05
Hello, can maybe someone Confirm that the first example releated to this: https://getakka.net/articles/intro/use-case-and-deployment-scenarios.html using FluentConfig is absolete and have to be updated ?