-
Notifications
You must be signed in to change notification settings - Fork 432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions about 3.0 release #1667
Comments
@rdjjke can you please answer some questions about the feature that you implemented? |
Can someone at least confirm that the upgrade path is just "install the new version"? |
|
There are some issues with |
Hi @x4m, what kind of issues with |
I tried asking on Slack, but the channel is dead, and I don't have Telegram.
How exactly does the new failover storage work?
Does it automatically sync the failover back to the primary storage once it comes back, or does that need to be set up externally?
Do you get warnings (or higher) logged when it's failing-over, or is it silent?
Can you set a limit for the amount of failover to use before it returns to the previous behaviour, making the DB retry until it's working again?
Also, I assume due to no mention in the release notes, that there's no breaking changes and you can just upgrade without changing anything?
The text was updated successfully, but these errors were encountered: