MySQL Forums :: NDB clusters :: Mass crashes of MySQL APIs (mysqld).

Advanced Search

Re: Mass crashes of MySQL APIs (mysqld).
Posted by: Stefan Auweiler ()
Date: November 10, 2016 11:04PM


thanks for the reply and sorry for the late response. We are looking for a solution to omit this variable.
For now, we can't show a query without such query. We simply don't have queries without this variable.

Some indications, why we don't blame this variable:
- we don't see a reason, why mysqld should hand his parameter over to ndb engine, on the other hand, as several 10-20 mysqld are facing this bug in the same second, it must be something in ndb engine too.
- if it would steer an error in the mysqld, why are we getting this bug in 10-20 mysqld at the same second, while 40 others are still running?
- the variable hasn't been a problem for years now; did you change the code in that area?
- we only see this errors since we went to Cluster 7.4.9 on Solaris 11, which involved the upgrade to 7.4.9 binaries on Solaris 10 clients

Do you have any other hint?
Any Idea about the 4010, Daniel mentioned?

Thanks, BR Stefan

Options: ReplyQuote

Subject Views Written By Posted
Mass crashes of MySQL APIs (mysqld). 619 Daniel Schroers 10/13/2016 08:14AM
Re: Mass crashes of MySQL APIs (mysqld). 285 Jon Stephens 10/14/2016 03:16AM
Re: Mass crashes of MySQL APIs (mysqld). 246 Stefan Auweiler 11/10/2016 11:04PM
Re: Mass crashes of MySQL APIs (mysqld). 204 Jon Stephens 11/12/2016 11:59AM

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.