-
Notifications
You must be signed in to change notification settings - Fork 61
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
[#224] Prefill a new server when doing a switch-to
#225
Conversation
When a `switch-to` operation is issued, the old server is flushed (i.e., connections are closed) and new connections to the new primary server are established. When such connections are established, the system does a full prefill against the new primary, so that when the `switch-to` completes, the new primary is prefilled as the old one was. Adds also a better detail about the server that is going to be flushed. Close agroal#224
Looking at it - there are 2 places where For 1) we know that a new primary has been selected. For 2) we know that the primary is the same. So, I think we can just change Thoughts ? |
Whenever the primary host is changed, by means of an explicit `switch-to` command or by a primary failure, the connection flushing is activated. If possible, the prefill should be also restored on the new server. As suggested in <agroal#225 (comment)> it would be nice to check if the specified new server is the same as the old one (failure of the primary) or a different one (`switch-to`), and in the case they are different the prefill is forced.
I've crated #226 as a possible implementation of your suggestion. |
The |
Got it, thanks. |
Whenever the primary host is changed, by means of an explicit `switch-to` command or by a primary failure, the connection flushing is activated. If possible, the prefill should be also restored on the new server. As suggested in <agroal#225 (comment)> it would be nice to check if the specified new server is the same as the old one (failure of the primary) or a different one (`switch-to`), and in the case they are different the prefill is forced. The prefill will always be to the `INITIAL` size when needed. If the primary is not set, there is no need to prefill with the `MIN_SIZE` value. Close agroal#224
Whenever the primary host is changed, by means of an explicit `switch-to` command or by a primary failure, the connection flushing is activated. If possible, the prefill should be also restored on the new server. As suggested in <agroal#225 (comment)> it would be nice to check if the specified new server is the same as the old one (failure of the primary) or a different one (`switch-to`), and in the case they are different the prefill is forced. The prefill will always be to the `INITIAL` size when needed. If the primary is not set, there is no need to prefill with the `MIN_SIZE` value. Close agroal#224
Whenever the primary host is changed, by means of an explicit `switch-to` command or by a primary failure, the connection flushing is activated. If possible, the prefill should be also restored on the new server. As suggested in <#225 (comment)> it would be nice to check if the specified new server is the same as the old one (failure of the primary) or a different one (`switch-to`), and in the case they are different the prefill is forced. The prefill will always be to the `INITIAL` size when needed. If the primary is not set, there is no need to prefill with the `MIN_SIZE` value. Close #224
Whenever the primary host is changed, by means of an explicit `switch-to` command or by a primary failure, the connection flushing is activated. If possible, the prefill should be also restored on the new server. As suggested in <#225 (comment)> it would be nice to check if the specified new server is the same as the old one (failure of the primary) or a different one (`switch-to`), and in the case they are different the prefill is forced. The prefill will always be to the `INITIAL` size when needed. If the primary is not set, there is no need to prefill with the `MIN_SIZE` value. Close #224
When a
switch-to
operation is issued, the old server is flushed(i.e., connections are closed) and new connections to the new primary
server are established.
When such connections are established, the system does a full prefill
against the new primary, so that when the
switch-to
completes, thenew primary is prefilled as the old one was.
Adds also a better detail about the server that is going to be
flushed.
Close #224