MySQL Restart - what happens

rocketman

OK, so in huntin g down why some users are prevented from logging in whist those that are already logged in happily keep on working, I discovered that MySQLd.exe starts out at around 400 Mb after a server restart and happily stays like that for a good part of the day. Then something happens (Still need to figure out what) and MySQLd.exe can jump to as high as 1.8 Gb

So Question. If AwareIM is running and users are logged in, what would happen if I did a restart on the MySQL service? Would everyone get kicked out or would things just hang until MySQL came back up again.

The reason I'm asking is that whilst MySQLd is below 1GB, everything seems to work fine It just seems that when it gets to a very high number that users get locked out. This may be a total red herring but I've got to try and bottom this one out somehow.

Don't want to find out the hard way - Thanks in advance

Rennur

Optimise your MySQL settings. My MySQL memory usage jumps to 10GB on occasion.

You might find kklosson's post Scaling Challenges useful.

Cheers

kklosson

You definitely will. 🙂

Rennur

If AwareIM is running and users are logged in, what would happen if I did a restart on the MySQL service? Would everyone get kicked out or would things just hang until MySQL came back up again.

Restarting your MySQL instance will not kick out any logged-in users. As soon as MySQL service is back up and running, your app will resume normal operation.

rocketman

Thanks for the responses guys - and I'll check out Klosson's post

On checking the Event Viewer I found these every time the lockup occured

The program java.exe version 8.0.1310.11 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1588
Start Time: 01d322a543ee3ebd
Termination Time: 4294967295
Application Path: c:\AwareIM\JDK\bin\java.exe
Report Id: a88df8ad-8e98-11e7-80dd-00505603a4f4
Faulting package full name:
Faulting package-relative application ID:

Not sure whether that was me shutting down AIM or the cause of the lockup?