Aaronontheweb on 1.4.14
Aaronontheweb on master
Bump Mongo2Go from 2.2.14 to 2.… Bump MongoDB.Driver from 2.11.4… Bump Microsoft.NET.Test.Sdk fro… and 4 more (compare)
Aaronontheweb on 1.4.14
Aaronontheweb on dev
Added v1.4.14 release notes (#1… (compare)
Aaronontheweb on dev
ensure that all recovered Times… (compare)
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?
NewtonSoftJsonSerializer
Hey guys,
I have data duplication issue when using TCP. I'm sending from "for" loop on client and reply with the same message from akka (echo).
If the message size 15 bytes + 4 for length, everything is perfect (sent 20k messages that is arrived in order and no duplication).
If message size more than that, duplications arrived. The pattern here is 1,2,3,4,2,3,4,5,6,7,8,2,3,4,5,6,7,8,9,10, ... (not always)
From my investigation the issue caused by
I have a repro project and will send to anyone who volunteers for investigation :)
akka {
stdout-loglevel = DEBUG
loglevel = DEBUG
loggers=["Akka.Logger.Serilog.SerilogLogger, Akka.Logger.Serilog"]
log-config-on-start = on
actor {
provider = "cluster"
}
remote {
dot-netty.tcp {
hostname = "127.0.0.1"
port = 8081
maximum-frame-size = 256000b
}
}
cluster {
seed-nodes = ["akka.tcp://tradex@127.0.0.1:4053"] # address of seed node
roles = ["ordersync", "logger"] # roles this member is in
role.["ordersync"].min-nr-of-members = 3 # crawler role minimum node count
# auto downing is NOT safe for production deployments.
# you may want to use it during development, read more about it in the docs.
#
# auto-down-unreachable-after = 10s
}
}