Mysql cluster restart errors


Version: Mysql 5.5.29 cluster 7.2.10

After some modifications of the config.ini, and a reload of the manager, when rolling restart the data nodes, the error happens. 

My case: I increased the IndexMemory and MaxNoOfConcurrentOperations, but the restart of the data node failed with error as below.

Time: Monday 22 April 2013 - 10:30:06
Status: Temporary error, restart node
Message: WatchDog terminate, internal error or massive overload on the machine running this node (Internal error, pr
ogramming error or missing error message, please report a bug)
Error: 6050
Error data: Allocating memory
Error object: /pb2/build/sb_0-7932439-1355951739.99/mysql-cluster-gpl-7.2.10/storage/ndb/src/kernel/vm/WatchDog.cpp
Program: ndbd
Pid: 9927
Version: mysql-5.5.29 ndb-7.2.10
Trace: /media/datadisk/mysql

Reason: The overload of memory usage.

Solution:
Decrease the number of parameter MaxNoOfConcurrentOperations back to 1000000. And keep the increased value of IndexMemory. 

Comments

Post a Comment

Popular posts from this blog

install postgreSQL in ubuntu 16.04

When following the Install PostgreSQL in Ubuntu  in Ubuntu 16.04, got error as below: $ apt-get install postgresql-9.6 Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: adobereader-enu:i386 : Depends: libgtk2.0-0:i386 (>= 2.4) but it is not going to be installed postgresql-9.6 : Depends: postgresql-client-9.6 Depends: postgresql-common (>= 171~) but it is not going to be installed Recommends: postgresql-contrib-9.6 but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). The suggested solution in the last line and a normal ubuntu upgrade do not solve the issue,  and the cmd below can fix it: $sudo apt full-upgrade After the fix, then can apt-get to install postgresql again. After install postgresql,
Keep reading

timestamp with 16, 13 and 10 digits to Qlik date

Sometimes, we need to convert the Linux timestamps to Qlik date, it can be done in the SQL script, and can also be done in the Qlik Load/expression. Linux timestamps with 16 digits are microseconds timestamps, and 13 digits are milliseconds, and 10 digits are second timestamps. To convert to a Qlik date, hour or time as following: As the timestamps starts from "19700101 00:00:00",  then this start timestamps needs be added: For 16 digits: Date(Date#('19700101', 'YYYYMMDD')+(SynchronousQuery_ Event_Time/1000000/86400) or  Date(25569+Round(SynchronousQuery_ Event_Time/1000000/86400),'YYYYMMDD') 25569 is the number format for date '19700101' For 13 digits: Date(Date#('19700101', 'YYYYMMDD')+(SynchronousQuery_ Event_Time/1000/86400) or  Date(25569+Round(SynchronousQuery_ Event_Time/1000/86400),'YYYYMMDD') For 10 digits: Date(Date#('19700101', 'YYYYMMDD')+(SynchronousQuery_ Event_T
Keep reading

install ipython in Cloudera VM using pip

I am practicing pyspark in Cloudera VM, and pyspack need be launched by ipython. In all the old Cloudera VM guide, it use easy_install to install ipython, but it does not work in Virtualbox 5.2.0 r118431 and later. And will get the error : $sudo easy_install ipython==1.2.1 ... error: Could not find suitable distribution for Requirement.parse('ipython==1.2.1') The solution for this is to use pip to install ipython. But by default, pip is not installed in cloudera VM, and pip can not be installed by eacy_install as well. And after some search, I  noticed cloudera has yum installed, and yum can install pip: $sudo yum install python-pip ... $which pip /usr/bin/pip Now ipython can be installed b pip: $sudo pip install ipython=1.2.1 ... Succesfully installled ipython-1.2.1 After that, launch spack by ipython: $PYSPARK_DRIVER_PYTHON=ipython pyspark ... Welcome to       ____                       __      / __ /__  ___ _____/  /__     _\ \/ _   \/  _  ` /  __/    '_ /
Keep reading