Fix MySQL/MariaDB round-stats SQL (GREATEST vs MAX) and throttle DB failure logging
Build / build (push) Successful in 1m14s
Build / build (push) Successful in 1m14s
This commit is contained in:
@@ -226,6 +226,12 @@ Common values:
|
||||
- `sslMode=VERIFY_IDENTITY` — TLS mandatory and the server certificate is validated
|
||||
against a trust store (production-grade; requires a properly signed/trusted cert).
|
||||
|
||||
MySQL and MariaDB are both supported through the same `mysql` driver/config. If a stats
|
||||
query ever fails (bad credentials, dropped connection, etc.), BlockParty logs the full error
|
||||
once for diagnosis and then throttles repeats of that same failure to once every 5 minutes —
|
||||
it never spams a stack trace on every round, and gameplay is unaffected either way since all
|
||||
stats I/O is async and best-effort.
|
||||
|
||||
The MySQL JDBC driver (`mysql-connector-j`) is bundled in the plugin jar, so no extra
|
||||
download is required. The stats table is created automatically on startup if it doesn't
|
||||
exist. All queries run asynchronously off the main thread regardless of storage type.
|
||||
|
||||
Reference in New Issue
Block a user