Table marked as crashed

Bug #535225 reported by Robert Jordan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OQGRAPH
In Progress
Undecided
OQgraph developers

Bug Description

When loading data into OQGRAPH MySQL is reporting:

ERROR 1194 (HY000): Table 'edges' is marked as crashed and should be repaired

Here is the query used to load data:

INSERT INTO edges (origid,destid) SELECT p_ino,st_ino FROM imd;

and here is a sample of the data being inserted:

+-----------+------------+
| p_ino | st_ino |
+-----------+------------+
| 113639424 | 113639425 |
| 113639424 | 111525270 |
| 113639424 | 381625582 |
| 113639424 | 3917221644 |
| 113639424 | 87451732 |
| 113639424 | 123690665 |
| 113639425 | 113639426 |
| 113639425 | 113704960 |
| 113639425 | 113836068 |
| 113639425 | 94051877 |
+-----------+------------+

System info:
MySQL = MariaDB 5.1.42

Revision history for this message
Robert Jordan (rjordan-imagemoversdigital) wrote :

Update:

This happens if the insert is greater than 35782820 rows.

Changed in oqgraph:
assignee: nobody → Antony T Curtis (atcurtis)
Revision history for this message
Arjen Lentz (arjen-lentz) wrote :

Robert, assigning this to Antony to check out - but this *may* be just a case of "out of memory".
There are some limitations of the storage engine API, sometimes the consequence is a "not quite appropriate" error code getting returned.

Perhaps you can help checking this also, but for instance running "free" in "watch" in another window while running the insert-select. thanks

Revision history for this message
Robert Jordan (rjordan-imagemoversdigital) wrote : RE: [Bug 535225] Re: Table marked as crashed

Hi Arjen,

I suspect you are correct. I have about 15M rows in the graph table now and memory is at 99%.

Thanks,
Robert

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Arjen Lentz
Sent: Wednesday, April 14, 2010 9:27 AM
To: Robert Jordan
Subject: [Bug 535225] Re: Table marked as crashed

Robert, assigning this to Antony to check out - but this *may* be just a case of "out of memory".
There are some limitations of the storage engine API, sometimes the consequence is a "not quite appropriate" error code getting returned.

Perhaps you can help checking this also, but for instance running "free"
in "watch" in another window while running the insert-select. thanks

--
Table marked as crashed
https://bugs.launchpad.net/bugs/535225
You received this bug notification because you are a direct subscriber of the bug.

Status in Graph Engine for MySQL, MariaDB and Drizzle: New

Bug description:
When loading data into OQGRAPH MySQL is reporting:

ERROR 1194 (HY000): Table 'edges' is marked as crashed and should be repaired

Here is the query used to load data:

INSERT INTO edges (origid,destid) SELECT p_ino,st_ino FROM imd;

and here is a sample of the data being inserted:

+-----------+------------+
| p_ino | st_ino |
+-----------+------------+
| 113639424 | 113639425 |
| 113639424 | 111525270 |
| 113639424 | 381625582 |
| 113639424 | 3917221644 |
| 113639424 | 87451732 |
| 113639424 | 123690665 |
| 113639425 | 113639426 |
| 113639425 | 113704960 |
| 113639425 | 113836068 |
| 113639425 | 94051877 |
+-----------+------------+

System info:
MySQL = MariaDB 5.1.42

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/oqgraph/+bug/535225/+subscribe

Revision history for this message
Arjen Lentz (arjen-lentz) wrote :

v3 should resolve this as it no longer stores its own data but instead shims on a regular engine for its persistent storage.

Changed in oqgraph:
assignee: Antony T Curtis (atcurtis) → OQgraph developers (oqgraph-dev)
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.