You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One game are having several issues caused by network instabilities and Nats-IO.
When we have a disruption in the communication between Nats and connector/game/metagame. It can't recover from that error. Even restarting the pods of pitaya doesn't solve the "nats timeout" error. We had to restart nats and pitaya together to solve the issue.
Logs
Here are a few logs from connector
{
"server": "connector",
"level": "error",
"version": "0.1.0",
"msg": "Failed to process remote: nats: timeout",
"source": "game",
"time": "2020-03-16T03:48:37Z"
}
I had this problem when I was creating a ruby pitaya framework, in my case was happening the following situation, when the metagame closes without remove your key on etcd the pitaya frontend didn't recognise that the metagame not exists anymore, so when the pitaya frontend receives a request they try send to an inexistent metagame server using the Nats then happens this "Nats timeout"
This is expected behavior, if the server is listed in etcd then we expect it to be answering to requests. That's why you should always insert the key for the server with a lease containing a ttl, so that it auto-heals after some few seconds.
Summary
One game are having several issues caused by network instabilities and Nats-IO.
When we have a disruption in the communication between Nats and connector/game/metagame. It can't recover from that error. Even restarting the pods of pitaya doesn't solve the "nats timeout" error. We had to restart nats and pitaya together to solve the issue.
Logs
Here are a few logs from connector
In our meta-game:
How to reproduce
Currently we couldn't reproduce the error. But it happened a few times:
When we did a reload on the network plugin. That interrupted some connections with nats and started the errors
When we got a slow consumer in Nats and some games restarted.
Related issues
I found this issue nats-io/stan.js#101
Versions
Nats: 1.1.0
Etcd: v3.3.10
The text was updated successfully, but these errors were encountered: