Re: ndb watchdog overslept
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.
Subject
Views
Written By
Posted
2302
February 08, 2017 11:44AM
1122
February 09, 2017 03:06PM
1485
February 11, 2017 08:40PM
754
February 14, 2017 06:12AM
846
February 20, 2017 05:17AM
Re: ndb watchdog overslept
960
February 21, 2017 04:36AM
839
February 21, 2017 05:27AM
799
February 21, 2017 06:04AM
909
February 21, 2017 08:34AM
847
February 21, 2017 10:38AM
777
February 22, 2017 08:38AM
Sorry, you can't reply to this topic. It has been closed.
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.