[MDEV-32991] Can't kill federatedx query when remote server is down Created: 2023-12-12  Updated: 2023-12-12

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - Federated
Affects Version/s: 10.11.6
Fix Version/s: 10.5, 10.6, 10.11

Type: Bug Priority: Minor
Reporter: MG Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: beginner-friendly, federated, federatedx


 Description   

During some testing in MDEV-32984 (with some create table examples that are relevant here), I noticed that the query will hang for a long time if you create the tables and then power off the server with the InnoDB base table:

  • create the federatedx table
  • turn off the server with the innodb table
  • issue a select *
  • restart mariadb takes around two minutes

If, instead of restart, you try first to "kill" the select in processlist, it switches from Query to Killed but hangs around in state Statistics for the full two minutes. I couldn't find a way to configure a timeout but perhaps the engine could kill the query more quickly, if it hasn't made a connection yet, and there is no need to eg rollback?



 Comments   
Comment by Sergei Golubchik [ 2023-12-12 ]

We can make federated to check whether it was killed directly before attempting a connection.
But I don't think it'll be possible to kill the query after it started connecting.

Generated at Thu Feb 08 10:35:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.