pt-online-schema-change not finding primary key

Reported by navigator93 on 2012-05-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Undecided
Daniel Nichter

Bug Description

When using 2.1.1 of the tool I had an issue with it not finding the primary key. The only way I could get it to use the simple numeric PK was by doing 2 things

1. changing the index detection query ti "select id from <tbl_name> where 1=1"...obviously that only worked because my primary key IS 'ID'
2. Also passing --chunk-index=Primary

doing #1 without #2 made it try to use a non unique other index which of course, at the copy data part.
Doing just #2 (as some bug in pt-tablechecksum indicates) just fails with this error
"Use of uninitialized value in string eq at /usr/bin/pt-online-schema-change line 2192."

Daniel Nichter (daniel-nichter) wrote :

This is probably the same problem as bug 978432 ("pt-table-checksum ignoring primary key").

tags: added: pt-online-schema-change
Changed in percona-toolkit:
status: New → Confirmed
status: Confirmed → Triaged
navigator93 (silviamikhail) wrote :

yup (and I know Baron said a lot of code there is common) but the fact that here even an explicit --chunk-index alone did not fix things made me think I should report it separately. I am have some debug snippets, if needed, but they ARE almost identical to the ones in bug 978432 :)

Baron Schwartz (baron-xaprb) wrote :

Daniel, is this fixed now?

Brian Fraser (fraserbn) on 2012-11-01
Changed in percona-toolkit:
assignee: nobody → Daniel Nichter (daniel-nichter)
Daniel Nichter (daniel-nichter) wrote :

This bug is very old and I bet it was fixed in some release between 2.1.1 and 2.1.9. Since there's no info or way to reproduce this bug in the original report, I'm going to close this as Invalid. If someone can reproduce this with 2.1.9, please reply with how to reproduce it.

Changed in percona-toolkit:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers