[MDEV-7108] Made long semaphore wait timeout configurable Created: 2014-11-13  Updated: 2018-02-13  Resolved: 2014-11-17

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Fix Version/s: 10.1.2

Type: Task Priority: Minor
Reporter: Jan Lindström (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MDEV-15295 Type mismatch for srv_fatal_semaphore... Closed

 Description   

https://github.com/facebook/mysql-5.6/commit/cd063ab930f05efdba39d504543998512d1bd71f

This diff introduced a new system variable fatal_semaphore_timeout,
it makes the fatal semaphore timeout configurable.

Its default/min/max vlaues are 600/1/2^32-1 in seconds (it was hardcoded
as 600, now its default value is 600, so the default behavior of this diff
should be no change).

 Comments   
Comment by Jan Lindström (Inactive) [ 2014-11-17 ]

commit 7bf391c2059f452eafb424336faa30d402f92b67
Author: Jan Lindström <jan.lindstrom@skysql.com>
Date: Mon Nov 17 09:55:55 2014 +0200

MDEV-7108: Make long semaphore wait timeout configurable

Merge Facebook commit https://github.com/facebook/mysql-5.6/commit/cd063ab93
0f05efdba39d504543998512d1bd71f
authored by Peng Tian from https://github.com/facebook/mysql-5.6

Introduced a new configuration variable innodb_fatal_semaphore_wait_threshol
d,
it makes the fatal semaphore timeout configurable. Modified original commit
so that no MariaDB server files are changed, instead introduced a new
InnoDB/XtraDB configuration variable.

Its default/min/max vlaues are 600/1/2^32-1 in seconds (it was hardcoded
as 600, now its default value is 600, so the default behavior of this diff
should be no change).

Generated at Thu Feb 08 07:17:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.