You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When engine shutdown is already in progress, the server is still running and listening for/processing incoming packets including possible login requests.
But during shutdown the security database is unavailable, therefore plugins may return auth failures.
In some cases (like all db users using same login) this may cause "banning" of login attempts (due to multiple login failures -- which is designed to manage DDOS attack conditions). This causes the related worker threads to sleep for a while before returning login failure to user. Such threads cause the shutdown process to pause, making it wait till the end of "ban period".
Currently there is no ability to restart FB instance from fbtest framework.
Though such test can be implemented by using 'sc.exe' and .bat with bulk ISQLs that are launched at the same time (Linux has, of course, similar tools for that task).
The text was updated successfully, but these errors were encountered:
description: When engine shutdown is already in progress server is still running and listening to incoming packets including possible login requests. But security database is unavailable, therefore plugins return auth failures. In some cases (like all users working with same login) this may cause banning of logins, i.e. worker threads will sleep for a while before replying login failure to user. Such threads prevent server shutdown making it wait till the end of ban period. => When engine shutdown is already in progress, the server is still running and listening for/processing incoming packets including possible login requests.
But during shutdown the security database is unavailable, therefore plugins may return auth failures.
In some cases (like all db users using same login) this may cause "banning" of login attempts (due to multiple login failures -- which is designed to manage DDOS attack conditions). This causes the related worker threads to sleep for a while before returning login failure to user. Such threads cause the shutdown process to pause, making it wait till the end of "ban period".
summary: Banned during engine shutdown threads cause unwanted delays when shutting server => Login attempts while engine is shutting down caused unnecessary delays in shutdown process
Test Details: Currently there is no ability to restart FB instance from fbtest framework.
Though such test can be implemented by using 'sc.exe' and .bat with bulk ISQLs that are launched at the same time (Linux has, of course, similar tools for that task).
Submitted by: @hvlad
When engine shutdown is already in progress, the server is still running and listening for/processing incoming packets including possible login requests.
But during shutdown the security database is unavailable, therefore plugins may return auth failures.
In some cases (like all db users using same login) this may cause "banning" of login attempts (due to multiple login failures -- which is designed to manage DDOS attack conditions). This causes the related worker threads to sleep for a while before returning login failure to user. Such threads cause the shutdown process to pause, making it wait till the end of "ban period".
Commits: dfc0259 fea7c61 a741300 9675ab2 87c306e
====== Test Details ======
Currently there is no ability to restart FB instance from fbtest framework.
Though such test can be implemented by using 'sc.exe' and .bat with bulk ISQLs that are launched at the same time (Linux has, of course, similar tools for that task).
The text was updated successfully, but these errors were encountered: