MySQL Forums :: NDB clusters :: ndb watchdog overslept


Advanced Search

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

That is what I mean.
When using --single-transaction the dump will start with
BEGIN TRANSACTION. So MySQL will try to use very large
transactions when importing the data into NDB. So if the
--single-transaction is removed the import will happen in
many small transactions instead which will avoid these
problems.

But obviously setting max_allowed_packet smaller also
somehow decreases the transaction size. Not sure exactly how
this happens.

Options: ReplyQuote


Subject Views Written By Posted
ndb watchdog overslept 275 d g 02/08/2017 11:44AM
Re: ndb watchdog overslept 148 Mikael Ronström 02/09/2017 03:06PM
Re: ndb watchdog overslept 169 d g 02/11/2017 08:40PM
Re: ndb watchdog overslept 100 d g 02/14/2017 06:12AM
Re: ndb watchdog overslept 115 d g 02/20/2017 05:17AM
Re: ndb watchdog overslept 116 Mikael Ronström 02/21/2017 04:36AM
Re: ndb watchdog overslept 76 Mikael Ronström 02/21/2017 05:27AM
Re: ndb watchdog overslept 103 d g 02/21/2017 06:04AM
Re: ndb watchdog overslept 84 Mikael Ronström 02/21/2017 08:34AM
Re: ndb watchdog overslept 75 d g 02/21/2017 10:38AM
Re: ndb watchdog overslept 82 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.