Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.29
Description
We have a customer continuously getting this in their error log:
InnoDB: Error (Duplicate key) writing word node to FTS auxiliary index table.
|
I haven't been able to reproduce this issue on my side. But looking through the source code, it doesn't seem like this type of error should be reported in the error log. Perhaps it could be better handled internally (silently ignored?).
This is a problem because it uselessly fills up the error log.
Thanks,
-will
2017-08-10 - A careful code review would be needed to answer the question if this has any user-visible impact, or why this occurs in the first place.
Attachments
Issue Links
- relates to
-
MDEV-12636 SELECT UNION writes garbage tail of VARCHAR column into internal temporary table
- Closed
-
MDEV-15237 "Can't write; duplicate key in table" when updating some rows in a transaction
- Closed
-
MDEV-19073 FTS row mismatch after crash recovery
- Closed
As demonstrated in
MDEV-11649andMDEV-12636, it is possible that FTS_DOC_ID sometimes is uninitialized garbage, causing this error.