[MDEV-31571] Missing error message or timeout, while using FederatedX engine and the remote database cannot be reached Created: 2023-06-28 Updated: 2023-07-03 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Information Schema, Storage Engine - Federated |
| Affects Version/s: | 10.9.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Karsten Budde | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | information_schema | ||
| Environment: |
centos7 |
||
| Description |
|
For about 2 days now, most queries on the information_schema tables do not bring any results within 10 minutes. Queries from Nagios sometimes hang longer than 6 hours in the process list. Even the query "select * from information_schema.key_column_usage limit 1;" does not bring any result within 10 minutes. The only change made on the database server is the installation of the Sentinel virus scanner. But even temporarily disabling Sentinel did not bring any improvement in the runtime of the above query. What can I do to find out why the above query is running so long? |
| Comments |
| Comment by Karsten Budde [ 2023-07-03 ] |
|
Hello, I think I figured out why the queries on the information_schema took so long. We had tables with the FederatedX storage engine pointing to an external server that could no longer be accessed through the firewall. After I deleted these tables, the queries are running fast again. It's a pity that in such a case there is no error message to indicate the problem. With kind regards |