Details
-
Type:
Task
-
Status: Stalled
-
Priority:
Minor
-
Resolution: Unresolved
-
Fix Version/s: 10.1
-
Component/s: None
-
Labels:None
Description
This is a request to improve the error logging in SHOW SLAVE STATUS output.
Specifically, the "Last_Error" and "Last_SQL_Error" have a size limit.
So the first request is to extend the size of this. Depending on the error, the relevant part may be omitted, and thus hard to track down.
Consider error 1071 (specified key is too long). If there a multiple keys, and the table definition is too long, then you don't even see any of the keys, such as the below:
Replicate_Wild_Ignore_Table:
Last_Errno: 1071
Last_Error: Error 'Specified key was too long; max key length is 3072 bytes' on query. Default database: 'test.dbname'. Query: 'CREATE TABLE `t1` (
...<trim long table def.>...
...
Skip_Counter: 0
Exec_Master_Log_Pos: 562164686
...
Second, perhaps for the case of error 1071, the actual offending key could be listed. That would be much improved, and make trouble-shooting a breeze.
For instance, something like "key ….. ( a, b, c ) was too long" would be ideal.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Similarly many other error messages could be extended to include the key name
backward incompatible changes to the errmsg.sys files — it's safer to do it in 10.1