View Issue Details

IDProjectCategoryView StatusLast Update
0000107EnvGeneralpublic2014-08-06 21:42
Reporterabdel-mawla Assigned Tooli  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
PlatformLinuxOSCentosOS Version6.x
Product Version1.0.2 
Target Version1.1.1 
Summary0000107: Error when starting an instance if SST is required
DescriptionStarting an instance in Galera Cluster system will produce an error if an SST will be performed while the actual state of the node is getting the date from the donor.
This leads to misunderstanding and searching in the error log files for what went wrong.

[root@gcservera ~]# su - mysql

Up : servera (5.6.13)

Down :

servera ( 3306) : cluster mysql performance_schema test

mysql@gcservera:~ [servera, 3306]> stop
.... SUCCESS!
mysql@gcservera:~ [servera, 3306]> v
1.0.2-RC1
mysql@gcservera:~ [servera, 3306]> rm /opt/mysql/data/grastate.dat
rm: remove regular file `/opt/mysql/data/grastate.dat'? y
mysql@gcservera:~ [servera, 3306]> start
............................................................ ERROR!
ERROR: Starting database servera failed (ret=225/rc=245).
ERROR: Try again with export MYENV_DEBUG=1 if you cannot find any reason...
mysql@gcservera:~ [servera, 3306]>

While if we used the mysql start script for the same situation, we can easily identify that an SST is taking place and no need to search in log files and so on:

[root@gcservera ~]# /etc/init.d/mysql stop
Shutting down MySQL.... [ OK ]
[root@gcservera ~]# rm /opt/mysql/data/grastate.dat
rm: remove regular file `/opt/mysql/data/grastate.dat'? y
[root@gcservera ~]# /etc/init.d/mysql start
Starting MySQL.................................SST in progress, setting sleep higher.. [ OK ]


Is it possible to print message like that in MyEnv instead of the error ?
Or at least keep printing dots (.....) until finishing the SST (MyEnv use 60 seconds timeout/sleep), so that the user will know that start process is at least in progress.

Notes:

1- SST method used in this example is: rsync
2- I think if the start process - in normal MySQL setup - required more than 60 seconds, the same error will be printed as well while in the background mysql service will continue starting. If that is true, so the problem is not only SST related but it could be easily produced in SST case.
3- Maybe this change should be related to myEnv.inc file:

    239 $lDebugOrig = $lDebug;
    240 $lDebug = '';
    241 for ( $i = 1; $i <= 60 ; $i++ ) {
    242
    243 sleep(1);
    244 echo ".";
    245 $ret = checkDatabase($aInstance);
    246 $rc = $ret;
    247 if ( $ret == 0 ) {
    248 break;
    249 }
    250 }
    251 $lDebug = $lDebugOrig;
    252
    253 if ( $rc == 0 ) {
    254 print " SUCCESS!\n";
    255 return($rc);
    256 }
    257 else {
    258 print " ERROR!\n";
    259 return($rc);
    260 }
TagsNo tags attached.

Activities

abdel-mawla

2014-02-07 09:02

reporter   ~0000083

I experienced the same problem in a normal MySQL setup when it had to create new "ib_logfile" files before starting the instance.
The new ib_logfile size is 256M and MySQL took more than 60 sec to get both files created which raised the error mentioned in this bug.

Issue History

Date Modified Username Field Change
2013-12-26 13:20 abdel-mawla New Issue
2013-12-26 13:20 abdel-mawla Status new => assigned
2013-12-26 13:20 abdel-mawla Assigned To => oli
2014-02-07 09:02 abdel-mawla Note Added: 0000083
2014-03-21 16:12 oli Project MyEnv => Env
2014-08-06 21:42 oli Target Version 1.0.3 => 1.1.1