MySQL Forums :: NDB clusters :: ndb watchdog overslept


Advanced Search

Re: ndb watchdog overslept
Posted by: Mikael Ronström ()
Date: February 21, 2017 04:36AM

Great that you found a way to get it working.
I think the problem you faced with 128M is that
it creates one big transaction using 128MByte of
information from mysqldump file. So when
decreasing this to 16M you decreased the size
of the transactions to a manageable size.

Disk pages involved in a transaction is bound to
the Disk Page Buffer until the transaction is
committed. So large transactions require a very
large DiskPageBufferMemory.

However it is still a bug that this causes a crash.
It should cause a transaction failure, but not a
crash.

Options: ReplyQuote


Subject Views Written By Posted
ndb watchdog overslept 210 d g 02/08/2017 11:44AM
Re: ndb watchdog overslept 123 Mikael Ronström 02/09/2017 03:06PM
Re: ndb watchdog overslept 125 d g 02/11/2017 08:40PM
Re: ndb watchdog overslept 73 d g 02/14/2017 06:12AM
Re: ndb watchdog overslept 74 d g 02/20/2017 05:17AM
Re: ndb watchdog overslept 75 Mikael Ronström 02/21/2017 04:36AM
Re: ndb watchdog overslept 50 Mikael Ronström 02/21/2017 05:27AM
Re: ndb watchdog overslept 70 d g 02/21/2017 06:04AM
Re: ndb watchdog overslept 54 Mikael Ronström 02/21/2017 08:34AM
Re: ndb watchdog overslept 53 d g 02/21/2017 10:38AM
Re: ndb watchdog overslept 59 d g 02/22/2017 08:38AM


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.