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
Various BOINC components don't properly close the DB connection they opened before. This is a problem because:
Open connections are a limited resource on the database server and new clients might be rejected when all are used up.
Left-open connections will eventually be aborted by the database server and logged as a WARNING, at least by MariaDB. MySQL still logs it as INFORMATION but MariaDB has a good reason to warn about those: the root cause can in fact be caused by misconfiguration (e.g. max_allowed_packet) or networking issues. Both should not get masked by otherwise harmless missing connection closing.
Sampling only the current C API (e.g. used by daemons), you'll find:
To be fair, in a web context it might be harder to decide if and when to close a connection as you might want to reuse it (opening connections is expensive). However, when you know it can be closed, it ought to be closed.
Various BOINC components don't properly close the DB connection they opened before. This is a problem because:
WARNING
, at least by MariaDB. MySQL still logs it asINFORMATION
but MariaDB has a good reason to warn about those: the root cause can in fact be caused by misconfiguration (e.g.max_allowed_packet
) or networking issues. Both should not get masked by otherwise harmless missing connection closing.Sampling only the current C API (e.g. used by daemons), you'll find:
boinc_db.open()
: 30boinc_db.close()
: 9This indicates a general issue, not just in the C API.
Thanks
The text was updated successfully, but these errors were encountered: