| Current Path : /usr/opt/mysql57/mysql-test/suite/ndb/r/ |
FreeBSD hs32.drive.ne.jp 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Wed Jan 14 12:18:08 JST 2015 root@hs32.drive.ne.jp:/sys/amd64/compile/hs32 amd64 |
| Current File : //usr/opt/mysql57/mysql-test/suite/ndb/r/ndb_mgm.result |
ndbd(s)
id=1 @127.0.0.1 (MYSQL_VERSION NDB_VERSION, Nodegroup: 0, *)
id=2 @127.0.0.1 (MYSQL_VERSION NDB_VERSION, Nodegroup: 0)
ndb_mgmd(s)
id=3 @127.0.0.1 (MYSQL_VERSION NDB_VERSION)
mysqld(s)
id=X @127.0.0.1 (MYSQL_VERSION NDB_VERSION)
id=X @127.0.0.1 (MYSQL_VERSION NDB_VERSION)
id=X @127.0.0.1 (MYSQL_VERSION NDB_VERSION)
id=X @127.0.0.1 (MYSQL_VERSION NDB_VERSION)
id=X @127.0.0.1 (MYSQL_VERSION NDB_VERSION)
id=X @127.0.0.1 (MYSQL_VERSION NDB_VERSION)
id=X (not connected, accepting connect from localhost)
id=X (not connected, accepting connect from localhost)
id=X (not connected, accepting connect from localhost)
id=X (not connected, accepting connect from localhost)
id=X (not connected, accepting connect from localhost)
id=X (not connected, accepting connect from localhost)
id=X (not connected, accepting connect from localhost)
id=X (not connected, accepting connect from localhost)
Missing report type specifier
ERROR: missing report type specifier!
Unknown report type specifier
ERROR: 'something' - report type specifier unknown!
ALL REPORT MEMORYUSAGE
Node 1: Data usage is X%(X XK pages of total X)
Node 1: Index usage is X%(X XK pages of total X)
Node 2: Data usage is X%(X XK pages of total X)
Node 2: Index usage is X%(X XK pages of total X)
1 REPORT MEMORYUSAGE
Node 1: Data usage is X%(X XK pages of total X)
Node 1: Index usage is X%(X XK pages of total X)
2 REPORT MEMORYUSAGE
Node 2: Data usage is X%(X XK pages of total X)
Node 2: Index usage is X%(X XK pages of total X)
Testing abbreviated form
Node 2: Data usage is X%(X XK pages of total X)
Node 2: Index usage is X%(X XK pages of total X)
Request memoryusage from non NDB node 3
ERROR: node 3 is not a NDB node!
Request memoryusage from non existing node 17
ERROR: node 17 is not a NDB node!
Request memoryusage from illegal nodeid 49
ERROR: illegal nodeid 49!
For the following, we want to be running ndbmtd with multiple
LQH threads
NDBD (1 instance) is ok, but 2 instances indicates ndbmtd
with proxy and only 1 real instance, not interesting.
cnf file should make this impossible
Following query should have no results
select node_id, count(1) as instances
from ndbinfo.threadblocks
where block_name="BACKUP"
group by node_id
having instances=2;
node_id instances
ALL REPORT BACKUPSTATUS
Node 1: Backup not started
Node 2: Backup not started
1 REPORT BACKUPSTATUS
Node 1: Backup not started
2 REPORT BACKUPSTATUS
Node 2: Backup not started
Testing HELP for REPORT
---------------------------------------------------------------------------
NDB Cluster -- Management Client -- Help for REPORT command
---------------------------------------------------------------------------
REPORT Displays a report of type <report-type> for the specified data
node, or for all data nodes using ALL
<report-type> =
BackupStatus - Report backup status of respective node
MemoryUsage - Report memory usage of respective node
EventLog - Report events in datanodes circular event log buffer
Missing dump arg
ERROR: Expected argument!
ERROR: Expected argument!
Illegal argument 4294967300
ERROR: Illegal value '4294967300' in argument to signal.
(Value must be between 0 and 0xffffffff.)
Illegal argument -1
ERROR: Illegal value '-1' in argument to signal.
(Value must be between 0 and 0xffffffff.)
Robustness issue with bug#14537622
Data node must not crash here
Sending dump signal with data:
0x000003e8 0x000003e8
Sending dump signal with data:
0x000003e8 0x000003e8
ALL DUMP 1
Sending dump signal with data:
0x00000001
Sending dump signal with data:
0x00000001
1 DUMP 1 2
Sending dump signal with data:
0x00000001 0x00000002
max DUMP args
Sending dump signal with data:
0x00000001 0x00000002 0x00000003 0x00000004
0x00000005 0x00000006 0x00000007 0x00000008
0x00000009 0x0000000a 0x0000000b 0x0000000c
0x0000000d 0x0000000e 0x0000000f 0x00000010
0x00000011 0x00000012 0x00000013 0x00000014
0x00000015 0x00000016 0x00000017 0x00000018
0x00000019
more than max DUMP args
ERROR: Too many arguments, max 25 allowed
test all report eventlog
note: test within quotes...
Missing argument
ERROR: Missing argument(s).
# Unknown argument
Invalid argument.
# CLUSTERLOG INFO
Severities enabled: INFO WARNING ERROR CRITICAL ALERT
# CLUSTERLOG OFF
Cluster logging is disabled
# Should be OFF now
Cluster logging is disabled.
# CLUSTERLOG ON
Cluster logging is enabled.
# Should be ON now
Severities enabled: INFO WARNING ERROR CRITICAL ALERT
# CLUSTERLOG TOGGLE
Cluster logging is disabled
# Should be OFF now
Cluster logging is disabled.
# CLUSTERLOG TOGGLE
Cluster logging is enabled.
# Should be ON now
Severities enabled: INFO WARNING ERROR CRITICAL ALERT
# Turn off severity INFO, ERROR and ALERT
ALERT disabled
INFO disabled
ERROR disabled
# Should not list ALERT, INFO or ERROR
Severities enabled: WARNING CRITICAL
# Turn off reaining severities
WARNING disabled
CRITICAL disabled
# Should not list anything
Severities enabled:
# Back to default severity
WARNING enabled
CRITICAL enabled
ALERT enabled
INFO enabled
ERROR enabled
# Should list default
Severities enabled: INFO WARNING ERROR CRITICAL ALERT
# Bogus severity
Invalid severity level: bogus1
# Should list default
Severities enabled: INFO WARNING ERROR CRITICAL ALERT
# Bug 11752837: start backup wait started should not print completion logs
Waiting for started, this may take several minutes
Node 1: Backup 1 started from node 3
# Bug 16585455: start backup with backup ID out of range
Invalid command: BACKUP 201303271430 WAIT COMPLETED
Backup ID out of range [1 - 4294967294]
Type HELP for help.
# Test 1/2 for Bug#16585497: abort backup with backup ID > 2^31
Abort of backup 2147483648 ordered
# Test 2/2 for Bug#16585497: abort backup with backup ID out of range
Invalid arguments: <BackupId> out of range [1-4294967294]