Adam D wrote:
All ALTER TABLE in 4.1 and 5.0 is done by recreating the table, this is why it takes
time. Work is underway as we speak to do many changes much faster. The problem
you've bumped into very much looks like a bug. 4116 is more or less an internal
error code which means that the NDB handler has done something not according
to the definition of the API towards the cluster.
So please file a bug report with as much info as you can provide.
Rgrds Mikael
> This table has 13million odd rows, I thought
> dropping an index would be as quick as dropping a
> table, but it seems to have to manipulate each
> row. It took forever, it ran overnight, so i typed
> in show warnings in case it didnt work and i got
> this back.
>
> mysql> drop index someId on tablename;
> ERROR 1296 (HY000): Got error 1 'Unknown error
> code' from ndbcluster
> mysql> show warnings;
> +-------+------+----------------------------------
> --------------------------------------------------
> ----------+
> | Level | Code | Message
>
> |
> +-------+------+----------------------------------
> --------------------------------------------------
> ----------+
> | Error | 1296 | Got error 1 'Unknown error code'
> from ndbcluster
> |
> | Error | 1296 | Got error 4116 'Operation was not
> defined correctly, probably missing a key' from
> NDB |
> | Error | 1296 | Got error 4116 'Operation was not
> defined correctly, probably missing a key' from
> ndbcluster |
> | Error | 1180 | Got error 4116 during COMMIT
>
> |
> +-------+------+----------------------------------
> --------------------------------------------------
> ----------+
> 4 rows in set (0.00 sec)
>
> # perror --ndb 4116
> OS error code 4116: Operation was not defined
> correctly, probably missing a key: Permanent
> error: Application error
>
> Ive never sucsessfully changed the structure of
> this table of 13million rows - I always get some
> form of error. Anyone have an idea as to whats
> happened here and or how to configure cluster so
> that sctructure changes are possible on such a
> large table.
Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog:
http://mikaelronstrom.blogspot.com