Using InnoDB engine instead of MyISAM
During the ZrT TM Cup, I worked on ManiaControl optimizations with 30 servers with 100 players linked to the same database. I already reported some optimizations for the Local Records Plugin but I also made a change with the Database Engine for all ManiaControl tables.
By default, they use MyISAM, but I decided to switch to InnoDB to increase performance that is vital with multi-servers on the same database. It makes a big changes with table locks, especially with Local Records Plugin where all servers can edit the table at the same time.
For simple and small servers, the impact is null, but for large and multi-servers the change is critical.
Worked around the issue with:
.:53 {
fanout . 127.0.0.1:5301
}
.:5301 {
forward . tls://9.9.9.9 {
tls_servername dns.quad9.net
}
}
@Funami580 This is interesting issue, I think it should be reopened.
@Funami580 Do you have an idea where problem can be in code?
Also interesting... Is corefile
fanout . tls://9.9.9.9 {
tls-server dns.quad9.net
}
working correctly?
Do you have an idea where problem can be in code?
No, but once https://github.com/networkservicemesh/fanout/pull/37 is merged, it is possible to see a more detailed error message, I guess.
Is corefile [...] working correctly?
Didn't I test that already with
.:5305 {
fanout . tls://9.9.9.9 {
tls-server dns.quad9.net
}
}
?
No, but once #37 is merged, it is possible to see a more detailed error message, I guess.
There was a minor comment related to error messages. Finally merged.
@Funami580 #37 is merged. Could you please retest the setup and provide new logs?
Thanks!
Oct 17 19:27:42 name coredns[176385]: [ERROR] plugin/errors: 2 archlinux.org. A: attempt limit has been reached, last err: dial tcp-tls: unknown network tcp-tls