We have a our database managed by DigitalOcean and a few days ago whilst our DB was overloaded we got a peculiar error in our Rails project which after looking into it quite a bit the only thing that I believe could have explained it, is if the standby node has a different DB version than the primary node. Is this possible in DO?
Unfortunately, I don’t have access to our DO stack at work, to check what exactly happened, but this question is more about curiosity than fixing the bug since it only happened once under very strange conditions.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
No, it’s not possible and Standby nodes are exact copies of the primary node (including DB version) that automatically take over if the primary node fails. You might have to look into it further to find the root cause but that won’t be the reason for sure.
If you have any logs or behavior which you can explain then you can reach out to support for more clarity.
Yes, for MySQL databases at least. I have had a primary node fail, and it automatically switched over to a standby.
The version of MySQL server changed from 8.0.20 to 8.0.23 .
Therefore the standby node had been already at a different version to the primary.