After restart the deamon is running but is "unconnectable". Can't connect with a client and heavily using disk I/O. I guess I have to wait another 10 hours ... :-/ I guess after restart mysqld is trying to again perform a rollback and hopes to be more successfull when running this single thread only without "external" impulses?
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
4 5 17808 3344272 167180 10741064 0 0 19 229 1 1 5 0 94 0
2 1 17808 3300160 167204 10747768 0 0 2960 103145 9619 14716 9 1 88 2
2 2 17808 3256020 167220 10753936 0 0 3388 106185 9899 14819 10 1 87 3
3 1 17808 3224908 167268 10761292 0 0 3502 117150 11639 18158 11 1 86 3
4 1 17808 3156580 167288 10768228 0 0 4087 125337 9606 13510 9 1 87 3
This is definitely unusable in production environment if there is a behaviour like this, unfortunately.... :-(
I guess we will hear eachother again tomorrow with more feedback.
After restart the deamon is running but is "unconnectable". Can't connect with a client and heavily using disk I/O. I guess I have to wait another 10 hours ... :-/ I guess after restart mysqld is trying to again perform a rollback and hopes to be more successfull when running this single thread only without "external" impulses?
procs ------- ----memory- ------- -- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
4 5 17808 3344272 167180 10741064 0 0 19 229 1 1 5 0 94 0
2 1 17808 3300160 167204 10747768 0 0 2960 103145 9619 14716 9 1 88 2
2 2 17808 3256020 167220 10753936 0 0 3388 106185 9899 14819 10 1 87 3
3 1 17808 3224908 167268 10761292 0 0 3502 117150 11639 18158 11 1 86 3
4 1 17808 3156580 167288 10768228 0 0 4087 125337 9606 13510 9 1 87 3
This is definitely unusable in production environment if there is a behaviour like this, unfortunately.... :-(
I guess we will hear eachother again tomorrow with more feedback.