MySQL Bugs: #31772: Select statement got warning after add a long name log/data file

Bug #31772	Select statement got warning after add a long name log/data file
Submitted:	23 Oct 2007 2:33	Modified:	19 Feb 2009 15:15
Reporter:	li zhou	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Disk Data	Severity:	S3 (Non-critical)
Version:	5.1.22	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
1.
===========
We create a logfile group with a long name log file.

Then we alter the logfile group to add a new long name log file.

When we do 'select * from information_schema.files", we got a warning  "Got temporary error 702 'Request to non-master' from NDB" and the row number in the information_schema.files is not correct.

2.
==========
We create a normal logfile group and create a tablespace with long name data file.
The select statement return "Empty set" and a warning message the same with above.

How to repeat:
mysql> CREATE LOGFILE GROUP lg1 ADD UNDOFILE './tmplogfile/path1/path2/path3/path4/path5/path6/path7/path8/path9/ThisisalongfilenameoflogfileThisisalongfilenameoflogfile.dat' INITIAL_SIZE 16M UNDO_BUFFER_SIZE = 1M ENGINE NDB;
Query OK, 0 rows affected (2.04 sec)

mysql> select * from information_schema.files;
................
................
3 rows in set (0.05 sec)

mysql> alter LOGFILE GROUP lg1 ADD UNDOFILE './tmplogfile/path1/path2/path3/path4/path5/path6/path7/path8/path9/ThisisalongfilenameoflogfileThisisalongfilenameoflogfile02.dat' INITIAL_SIZE 4M ENGINE NDB;
Query OK, 0 rows affected (0.68 sec)

mysql> select * from information_schema.files;
...............
...............
2 rows in set, 1 warning (0.00 sec)

mysql> show  warnings;
+-------+------+----------------------------------------------------------+
| Level | Code | Message        |
+-------+------+----------------------------------------------------------+
| Error | 1297 | Got temporary error 702 'Request to non-master' from NDB |
+-------+------+----------------------------------------------------------+
1 row in set (0.00 sec)

==========================

mysql> CREATE LOGFILE GROUP lg1 ADD UNDOFILE 'logfile.dat' INITIAL_SIZE 16M UNDO_BUFFER_SIZE = 1M ENGINE NDB;
Query OK, 0 rows affected (1.86 sec)

mysql> select * from information_schema.files;
..............
..............
3 rows in set (0.05 sec)

mysql> alter LOGFILE GROUP lg1 ADD UNDOFILE 'logfile02.dat' INITIAL_SIZE 4M ENGINE NDB;
Query OK, 0 rows affected (0.70 sec)

mysql> select * from information_schema.files;
..................
..................
5 rows in set (0.01 sec)

mysql> CREATE TABLESPACE ts1 ADD DATAFILE './tmpdatafile/path1/path2/path3/path4/path5/path6/path7/path8/path9/ThisisalongfilenameofdatafileThisisalongfilenameofdatafile.dat' USE LOGFILE GROUP lg1 INITIAL_SIZE 12M ENGINE NDB;
Query OK, 0 rows affected (1.55 sec)

mysql> select * from information_schema.files;
Empty set, 1 warning (0.01 sec)

mysql> show  warnings;
+-------+------+----------------------------------------------------------+
| Level | Code | Message        |
+-------+------+----------------------------------------------------------+
| Error | 1297 | Got temporary error 702 'Request to non-master' from NDB |
+-------+------+----------------------------------------------------------+
1 row in set (0.00 sec)

Suggested fix:
Return right messge when we do select statement from information_schema.files.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/66895

2847 Jonas Oreland	2009-02-19
      ndb - bug#31769 bug#31772 bug#31770 - fix path name longer than MAX_TAB_NAME, i.e use PATH_MAX is several places

Pushed into 5.1.32-ndb-6.2.17 (revid:jonas@mysql.com-20090219122238-h87lxgiiur7xwdl8) (version source revid:jonas@mysql.com-20090219122238-h87lxgiiur7xwdl8) (merge vers: 5.1.32-ndb-6.2.17) (pib:6)

Pushed into 5.1.32-ndb-6.3.23 (revid:jonas@mysql.com-20090219123956-j8x3hj0ae2xwyduz) (version source revid:jonas@mysql.com-20090219123956-j8x3hj0ae2xwyduz) (merge vers: 5.1.32-ndb-6.3.23) (pib:6)

Pushed into 5.1.32-ndb-6.4.3 (revid:jonas@mysql.com-20090219125659-ld2mlhzpqj9tfg9u) (version source revid:jonas@mysql.com-20090219125659-ld2mlhzpqj9tfg9u) (merge vers: 5.1.32-ndb-6.4.3) (pib:6)

Documented bugfix in the NDB-6.2.17, 6.3.23, and 6.4.2 changelogs. See Bug #31769 for changelog entry.