Thanks for your help. I must confess that although I am usually a
competent systems administrator I am not a C programmer so slightly
lost you in your previous email!
I think that the bit of the trace you are interested is this:
NDBFS 000915 000917 000728 000934
CMVMI 000450 000458
QMGR 001815 001833
--------------- Signal ----------------
r.bn: 252 "QMGR", r.proc: 3, r.sigId: 646 gsn: 235 "DISCONNECT_REP" prio: 0
s.bn: 254 "CMVMI", s.proc: 3, s.sigId: 645 length: 2 trace: 8 #sec: 0 fragInf: 0
NodeId: 2, ErrorCode: 0
--------------- Signal ----------------
r.bn: 254 "CMVMI", r.proc: 3, r.sigId: 645 gsn: 235 "DISCONNECT_REP" prio: 0
s.bn: 0 "API", s.proc: 3, s.sigId: 644 length: 2 trace: 8 #sec: 0 fragInf: 0
NodeId: 2, ErrorCode: 0
--------------- Signal ----------------
r.bn: 253 "NDBFS", r.proc: 3, r.sigId: 644 gsn: 164 "CONTINUEB" prio: 0
s.bn: 253 "NDBFS", s.proc: 3, s.sigId: 643 length: 1 trace: 0 #sec: 0 fragInf: 0
Scanning the memory channel every 10ms
--------------- Signal ----------------
r.bn: 253 "NDBFS", r.proc: 3, r.sigId: 642 gsn: 164 "CONTINUEB" prio: 0
s.bn: 253 "NDBFS", s.proc: 3, s.sigId: 641 length: 1 trace: 0 #sec: 0 fragInf: 0
Scanning the memory channel every 10ms
--------------- Signal ----------------
And so on. The complete file can be downloaded at
http://www.davz.net/general/ndb_3_trace.log.3.
Please let me know if you want any other information. Can I just
confirm that it *is* possible to run a totally redundent cluster on
three servers - two API/storage nodes and one node for managment.
(when I say totally redundent I mean you can pull the power plug out
of any one server with no effect on the overall system).
With many thanks,
Alex
