MySQL Forums :: NDB clusters :: NDB engine possibly not a realtime database engine?


Advanced Search

Re: NDB engine possibly not a realtime database engine?
Posted by: Stefan Auweiler ()
Date: March 17, 2017 01:49AM

Thanks for the reply, Mikael
we'll try to log and tweak NTP, to catch this.


How could I prove that this is coming from the OS?
Is there a call 'give me CPU' which is not answered for a while?
Is the log message a 100% prove of this?

Customer is really complaining about real time capabilities here.


We never noticed this message
2017-03-16 11:10:59 [ndbd] WARNING -- Ndb kernel thread 10 is stuck in: Job Handling elapsed=6336
on two systems in parallel.

If the one node doesn't respond within ms (as usual) why is the other nod of the node group not delivering instead?



BTW: we did not see this in Solaris 10 with NDB 7.3.7 but had to change binaries do go to Solaris 11, so we went to NDB 7.4.9.
Have there been any changes in this area?



Thanks
Stefan

Options: ReplyQuote


Subject Views Written By Posted
NDB engine possibly not a realtime database engine? 136 Stefan Auweiler 03/16/2017 05:27AM
Re: NDB engine possibly not a realtime database engine? 66 Mikael Ronström 03/16/2017 08:49AM
Re: NDB engine possibly not a realtime database engine? 94 Stefan Auweiler 03/17/2017 01:49AM
Re: NDB engine possibly not a realtime database engine? 88 Mikael Ronström 03/17/2017 02:43AM
Re: NDB engine possibly not a realtime database engine? 44 Gunther Marx 03/23/2017 04:25AM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.