MySQL Forums :: NDB clusters :: ndb watchdog overslept


Advanced Search

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

--single-transaction is actually not really supported for MySQL Cluster.
Cut from manual:
The --single-transaction option and the --lock-tables option are mutually exclusive because LOCK TABLES causes any pending transactions to be committed implicitly.

This option is not supported for MySQL Cluster tables; the results cannot be guaranteed to be consistent due to the fact that the NDBCLUSTER storage engine supports only the READ_COMMITTED transaction isolation level. You should always use NDB backup and restore instead.

To dump large tables, combine the --single-transaction option with the --quick option.

So when you make a mysqldump, avoid the single-transaction part, this will
remove the need for massively large transactions while restoring the data.

Options: ReplyQuote


Subject Views Written By Posted
ndb watchdog overslept 285 d g 02/08/2017 11:44AM
Re: ndb watchdog overslept 152 Mikael Ronström 02/09/2017 03:06PM
Re: ndb watchdog overslept 175 d g 02/11/2017 08:40PM
Re: ndb watchdog overslept 101 d g 02/14/2017 06:12AM
Re: ndb watchdog overslept 119 d g 02/20/2017 05:17AM
Re: ndb watchdog overslept 119 Mikael Ronström 02/21/2017 04:36AM
Re: ndb watchdog overslept 77 Mikael Ronström 02/21/2017 05:27AM
Re: ndb watchdog overslept 107 d g 02/21/2017 06:04AM
Re: ndb watchdog overslept 87 Mikael Ronström 02/21/2017 08:34AM
Re: ndb watchdog overslept 77 d g 02/21/2017 10:38AM
Re: ndb watchdog overslept 84 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.