maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #05996
Problem with InnoDB: Semaphore wait after upgrading to 10.3.27
-
To:
"maria-discuss@xxxxxxxxxxxxxxxxxxx" <maria-discuss@xxxxxxxxxxxxxxxxxxx>
-
From:
Conor Murphy <conor_mark_murphy@xxxxxxxxxxx>
-
Date:
Tue, 16 Mar 2021 13:58:11 +0000
-
Accept-language:
en-IE, en-US
-
Arc-authentication-results:
i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
-
Arc-message-signature:
i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VfE4tDfBEScqRYzFEXjPfcji7rT4Mhf3HmbZJBhjOEA=; b=Rs4dzXSCvCcEHigNk2UUnXb9JqHGFh1hpVvpERCCAiZSA2rlVyHA+YbRHaBjjm6iKaCai2IMbgmkmiVf+kBcR5oD8+3t3toeMP39ZoDDxZFtnpLVB6sJeXcxogi455RlECFwuEdd4r1o8MNwOliz55/6ZM4qlbZeX47cfjXSyPp2wULUAbQITjDHpx95L9os8Aur0p5fP7VcAU3+quuCN2A97FRD6GMTYvRnn6n4R34hpXHkKX9N0rTVzpMnrLZIFH3TCFOYBLkMty/uscBGOBWfHamy+n3tUVSKPcCx9D6AmSe+kIg83wN4FO5JCIKsPfkSNesuWkovRhz7ItReOw==
-
Arc-seal:
i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J++cts71KlS7X8P2kblXl4Y2T1eVCB+BDc7/DHdPqDe02feqj30aevJ4UFw8odR3ns7TbRl5ppm+HYwXXx/xjE8EwfupcmsvSY5SZQervqQdkmWCIykpYYyLo59k20k+ddF4FzGwEwbrQtSoKu1Jaxn+DlF/o7WV/nPfC2Iqk1oqZkNIc9McCEBFVExOQJjqCG+hrzK1BeXKOV7KX4o7cOCzAUZteMrjoPuqpb2JhbLv7zIBMSkNY8+FiDTNpbtGB2XLwRrB4dUBprz2CKArpRDnEN8iVo5TidPuBkYFXHEIeKfakGdlgyeV1tiV0WgUZTgbnW9LM8vaT8ZNRrYfmw==
-
Thread-index:
AQHXGmsGUul9p7yyW0a/9UFyTcI2dg==
-
Thread-topic:
Problem with InnoDB: Semaphore wait after upgrading to 10.3.27
Hi,
We have a handful of servers running MariaDB 10.3. We noticed issues on two of them where we were getting issues like "InnoDB: A long semaphore wait:--Thread 140602802394880 has waited at dict0stats.cc line 1969 for 241.00 seconds the semaphore:" and crashes like "ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.210215 7:14:24 [ERROR] mysqld got signal 6 ;"
Turned out that these two servers were running 10.3.27 whereas the others were running 10.3.17. After downgrading the two problem servers to 10.3.17, all the issues with InnoDB semaphores stopped.
Any ideas on how to track down what change between 10.3.17 to 10.3.27 might be causing this problem?
Thanks,
Conor
Follow ups
