We are trying to migrate away from the Docker Compose Redis instance. We’re still on Loraserver (the latest version before the name change to Chirpstack). We migrated the keys with this procedure: How To Migrate Redis Data to a DigitalOcean Managed Database | DigitalOcean. However it seems like we didn’t update the configuration correctly for the application server. So only the network server was pointing to the new instance. We didn’t discover this error before someone pointed out that our devices that are supposed to report data every minute, only reported data 4 times or so during an hour instead.
After fixing the configuration for the application server too, the data rate still hasn’t increased. So now we’re wondering if that wasn’t the problem in the first place, or if the time that went by where the application server and the network server were pointing at different Redis instances has messed something up. I couldn’t find out if there’s something in the documentation that says anything about how Redis specifically is used by both the application and network servers. Maybe I’ll have to dig through the source code?
Could it be something else that is messing this up? Could it be the extra latency introduced when the Redis instance is deployed in Amsterdam, and the Loraserver stack is deployed in Norway?
When I check the frames received and frames transmitted for gateways they are drastically reduced. The pictures below are screenshots of frames transmitted before migrating and then after.
Before , and after migrating
When adding a new device that reports every minute, it does so flawlessly. Any suggestions on what we can do to get the data rate back up without physically resetting all of our devices?