Re: ndb watchdog overslept
Posted by:
d g
Date: February 20, 2017 05:17AM
Hi,
after more testing i found the solution. The Problem was the System where the dump came from. On the Soucre System max-allowed-packet was configured to 128M. It seems that this value is too high and cause the ndb datanodes to overload. i dumped the data again with 16M Packet size with the following command and my restore runs without error but a bit slower:
ysqldump --hex-blob --routines --triggers --add-drop-database --single-transaction --max_allowed_packet=16M
Maybe 32M or 64M is also ok but i didnt tested it yet.
Regards
Denny
Subject
Views
Written By
Posted
1046
February 08, 2017 11:44AM
504
February 09, 2017 03:06PM
783
February 11, 2017 08:40PM
377
February 14, 2017 06:12AM
Re: ndb watchdog overslept
455
February 20, 2017 05:17AM
464
February 21, 2017 04:36AM
380
February 21, 2017 05:27AM
427
February 21, 2017 06:04AM
398
February 21, 2017 08:34AM
393
February 21, 2017 10:38AM
364
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.