Bug #88696 Autotest: atrt database wrongly configured to use cluster
Submitted: 29 Nov 2017 11:58 Modified: 19 Mar 2018 9:28
Reporter: Tiago Alves Email Updates:
Status: Closed Impact on me:
None 
Category:Tests: Cluster Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: Tiago Alves CPU Architecture:Any

[29 Nov 2017 11:58] Tiago Alves
Description:
When ATRT generates processes configuration it assumes all MySQL servers should have cluster connection options. While this might be true for MySQL servers used in testing, this is not the case for the ATRT database.

ATRT database is used to support testing (start and stop process on demand) and hence should be independent of the system under test.

How to repeat:
When generating cluster configuration for upgrade tests, atrt database has the following options:

[mysql_cluster.atrt]
ndb-connectstring=

[mysqld.1.atrt]
datadir= SOME_PATH
port= 10402
ndb-connectstring=
ndbcluster

[client.1.atrt]
host= HOST
socket= mysql.sock
port= 10402

When running tests, ATRT reports:

2017-11-28 16:37:28 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:31 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:34 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:37 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:40 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:43 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:46 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:49 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:52 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:55 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s
2017-11-28 16:37:58 [ndb_atrt] INFO     -- Retrying connect to HOST:10402 3s

And mysqld reports:

2017-11-28T17:35:17.985850Z 0 [Note] SOME_PATH/mysql-5.7-cluster-7.6/bin/mysqld: ready for connections.
Version: '5.7.20-ndb-7.6.4-debug'  socket: 'mysql.sock'  port: 10402  Source distribution
2017-11-28T17:35:17.985907Z 2 [Note] NDB Util: Wait for cluster to start
2017-11-28T17:35:17.986935Z 0 [Note] NDB Index Stat: Wait for cluster to start
2017-11-28T17:35:17.986954Z 1 [Note] NDB Binlog: Check for incidents
2017-11-28T17:35:17.986985Z 1 [Note] NDB Binlog: Wait for cluster to start
2017-11-28T17:35:47.990337Z 0 [Warning] NDB : Tables not available after 30 seconds.  Consider increasing --ndb-wait-setup value
2017-11-28T17:35:47.990411Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2017-11-28T17:35:47.990437Z 0 [Note] Beginning of list of non-natively partitioned tables
2017-11-28T17:35:48.008655Z 4 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.050245Z 4 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.223618Z 4 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.226949Z 4 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.376023Z 0 [Note] End of list of non-natively partitioned tables
2017-11-28T17:35:48.379986Z 5 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.384278Z 5 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.408355Z 5 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.428133Z 5 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.441063Z 5 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.452852Z 5 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:35:48.469028Z 5 [Warning] NDB: Failed to acquire global schema lock, error: (4009)Cluster Failure
2017-11-28T17:37:12.295623Z 7 [Note] Aborted connection 7 to db: 'atrt' user: 'root' host: '' (Got an error reading communication packets)

Suggested fix:
Update ATRT settings generation to skip cluster connection settings generation for ATRT database.
[29 Nov 2017 12:26] Umesh Shastry
Thank you for the report.
[19 Mar 2018 9:28] Jon Stephens
Fixed in NDB 7.2.33, 7.3.21, 7.4.19, 7.5.10, 7.6.5, 8.0.1.

Testing only, no changelog entry needed.

Closed.