[MDEV-14554] MariaDB server 10.2.10 doesn't repond on some requests Created: 2017-12-01  Updated: 2017-12-05  Resolved: 2017-12-05

Status: Closed
Project: MariaDB Server
Component/s: Platform Windows
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Michael Graf Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Windows Server 2016 Standard
RAM: 128 GB


Attachments: Text File 10.2.10-uniqstack.txt     Text File 10.2.11-uniqstack.txt     File MG-GUI-SSD1.err     PNG File MariaDB in Taskmanager.png     Text File Our application is waiting on data from MariaDB server.txt     File my.ini     Zip Archive mysqld.exe_10.2.11.zip     Zip Archive mysqld.exe_171201_165405.zip     Text File show full processlist.txt     Text File show global variables.txt    
Issue Links:
Relates
relates to MDEV-13941 Innodb/Windows, 10.2 : High NTFS fra... Closed

 Description   

Shortly after start of our application MariaDB doesn't repond on some requests any more.

A connection with MySQL Workbench can still be established.
Database queries like 'show global variables', 'show full processlist', ... can still be executed but some requests hang.



 Comments   
Comment by Michael Graf [ 2017-12-01 ]

MariaDB server 10.2.11 shows the same behaviour.
I attached also a minidump of MariaDB 10.2.11.

Comment by Michael Graf [ 2017-12-05 ]

After I thought MariaDB 10.2.10 is not responding on some requests a few minutes after the start of our application I exchanged MariaDB 10.2.10 through MariaDB 5.5.57.
There I could see the same effect.
Our application was waiting on the reponses of many database requests.
So I executed many "show full processlist" commands and I saw that MariaDB server was responding on the database requests but it was very, very slow.
The CPU performance was between 0-1%.
When I executed "contig -s d:\leutek\mariadb" the CPU was nearly 50%.
So, sorry for this wrong issue.

Comment by Vladislav Vaintroub [ 2017-12-05 ]

So, this is filesystem fragmentation issue, right?

Comment by Michael Graf [ 2017-12-05 ]

Yes, absolutely.

Comment by Vladislav Vaintroub [ 2017-12-05 ]

Might be consequence of NTFS fragmentation that plagued MariaDB until 10.2.10 (MDEV-13941)

Generated at Thu Feb 08 08:14:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.