Quantcast
Channel: MySQL Forums - NDB clusters
Viewing all articles
Browse latest Browse all 1560

Unable to start Node and API (1 reply)

$
0
0
Hi there, problem is my DB nodes are stuck at starting and API can't get connected.

my config.ini file as below:

[NDB_MGMD DEFAULT]
Portnumber=1186


[NDB_MGMD]
NodeId=51
HostName=192.168.168.151
DataDir=/opt/SQL/51/
Portnumber=1186
ArbitrationRank=1

[TCP DEFAULT]
SendBufferMemory=8M
ReceiveBufferMemory=8M

[NDBD DEFAULT]
BackupMaxWriteSize=1M
BackupDataBufferSize=16M
BackupLogBufferSize=4M
BackupMemory=20M
BackupReportFrequency=10
MemReportFrequency=30
LogLevelStartup=15
LogLevelShutdown=15
LogLevelCheckpoint=8
LogLevelNodeRestart=15
DataMemory=700M
IndexMemory=175M
MaxNoOfTables=4096
MaxNoOfTriggers=3500
NoOfReplicas=2
StringMemory=25
DiskPageBufferMemory=64M
SharedGlobalMemory=20M
LongMessageBuffer=32M
MaxNoOfConcurrentTransactions=16384
BatchSizePerLocalScan=512
FragmentLogFileSize=256M
NoOfFragmentLogFiles=5
RedoBuffer=64M
MaxNoOfExecutionThreads=2
StopOnError=false
LockPagesInMainMemory=1
TimeBetweenEpochsTimeout=32000
TimeBetweenWatchdogCheckInitial=60000
TransactionInactiveTimeout=60000
HeartbeatIntervalDbDb=1500
HeartbeatIntervalDbApi=1500
MaxNoOfConcurrentOperations=150000
MaxNoOfAttributes=10000
MaxNoOfOrderedIndexes=512

[NDBD]
NodeId=1
HostName=192.168.168.153
DataDir=/opt/MySQL_Cluster/1/

[NDBD]
NodeId=2
HostName=192.168.168.154
DataDir=/opt/MySQL_Cluster/2/


[MYSQLD DEFAULT]

[MYSQLD]
NodeId=61
HostName=192.168.168.151

[MYSQLD]
NodeId=63
HostName=192.168.168.152

[MYSQLD]
NodeId=65

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

Current status:

[root@SQL-Arbiter ~]# ndb_mgm -e show
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 2 node(s)
id=1 @192.168.168.153 (mysql-5.6.15 ndb-7.3.4, starting, Nodegroup: 0, *)
id=2 @192.168.168.154 (mysql-5.6.15 ndb-7.3.4, starting, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=51 @192.168.168.151 (mysql-5.6.15 ndb-7.3.4)

[mysqld(API)] 3 node(s)
id=61 (not connected, accepting connect from 192.168.168.151)
id=63 (not connected, accepting connect from 192.168.168.152)
id=65 (not connected, accepting connect from any host)


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

From the log,
[root@SQL-Arbiter 51]# tail -100 ndb_51_cluster.log

2015-02-24 16:55:09 [MgmtSrvr] INFO -- Node 1: Data usage is 0%(0 32K pages of total 22400)
2015-02-24 16:55:09 [MgmtSrvr] INFO -- Node 1: Index usage is 0%(0 8K pages of total 22432)
2015-02-24 16:55:09 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.152. Returned error: 'Id 63 already allocated by another node.'
2015-02-24 16:55:11 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.151. Returned error: 'Id 61 already allocated by another node.'
2015-02-24 16:55:11 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.152. Returned error: 'Id 63 already allocated by another node.'
2015-02-24 16:55:13 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.151. Returned error: 'Id 61 already allocated by another node.'
2015-02-24 16:55:14 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.152. Returned error: 'Id 63 already allocated by another node.'
2015-02-24 16:55:15 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.151. Returned error: 'Id 61 already allocated by another node.'
2015-02-24 16:55:16 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.152. Returned error: 'Id 63 already allocated by another node.'
2015-02-24 16:55:17 [MgmtSrvr] WARNING -- Failed to allocate nodeid for API at 192.168.168.151. Returned error: 'Id 61 already allocated by another node.'

Viewing all articles
Browse latest Browse all 1560

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>