[MDEV-31006] OQGraph query causes OOM-kill Created: 2023-04-04  Updated: 2023-11-28

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - OQGRAPH
Affects Version/s: 10.9.5
Fix Version/s: 10.11

Type: Bug Priority: Major
Reporter: Хүрэлхуяг Assignee: Andrew Hutchings
Resolution: Unresolved Votes: 0
Labels: bug, not-10.4


 Description   

I was experimenting with what OQGraph is capable of.
My first query was made my MariaDB server killed

The query:
`SELECT * FROM personParentGraph WHERE latch='dijkstras' AND origid=1 AND destid=2;`

My Backing table:

CREATE TABLE personParent (
 
  person_id INTEGER UNSIGNED,
 
  parent_id INTEGER UNSIGNED,
 
  PRIMARY KEY (person_id, parent_id),
 
  FOREIGN KEY (person_id) REFERENCES person(id) ON UPDATE CASCADE,
 
  FOREIGN KEY (parent_id) REFERENCES person(id) ON UPDATE CASCADE
 
);

I created OQGraph table with this DDL:

CREATE TABLE personParentGraph
 
    ENGINE=OQGRAPH
 
    data_table='personParent' origid='person_id' destid='parent_id';

SysLog:
OS: Ubuntu 22.04.1 LTS,

Version: mariadb-server 1:10.9.5+maria~ubu2204 amd64

Apr  4 19:58:19 localhost systemd[1]: mariadb.service: A process of this unit has been killed by the OOM killer.
 
Apr  4 19:58:20 localhost systemd[1]: mariadb.service: Main process exited, code=killed, status=9/KILL
 
Apr  4 19:58:20 localhost systemd[1]: mariadb.service: Failed with result 'oom-kill'.
 
Apr  4 19:58:20 localhost systemd[1]: mariadb.service: Consumed 20.742s CPU time.


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