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
Replication not restarting after network failure #7150
Comments
…re. Minor adjustments regarding replication startup errors
Please test the next snapshot build, it should be fixed there. |
Already tested from your build and I succeeded to run my tests. Hopefully 4.0.2 is coming soon :) |
@@@ QA issue @@@ |
Hello, P063ST101-1 (replica) Tue Sep 26 15:04:28 2023 P063ST101-1 (replica) Tue Sep 26 15:31:54 2023 P063ST101-1 (replica) Mon Oct 2 12:03:04 2023 P063ST101-1 (replica) Mon Oct 2 12:03:35 2023 P063ST101-1 (replica) Mon Oct 2 12:04:26 2023 |
Looks like network sometimes has connectivity problems. |
Oke I accept but in that case will the replication stop? It seems that the network was correct later on but the replication didn't continue and the number of files where increasing???? |
When Firebird starts and the configurerd journal_source_directory is inaccessible it does not retry later on. This behaviour would be nice when using a network share, the share might
not be available when firebird starts but can be available later on.
Perhaps I'm missing some settings but I noticed this behavior
With kind regards,
Leonard Wennekers
The text was updated successfully, but these errors were encountered: