Skip to content
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.

Commit

Permalink
Browse files Browse the repository at this point in the history
MySQL: Lock Wait Timeout
  • Loading branch information
joergsteffens committed Sep 12, 2017
1 parent 859641f commit 0ba27b5
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 1 deletion.
2 changes: 1 addition & 1 deletion manuals/en/main/bareos.sty
Expand Up @@ -656,7 +656,7 @@ Version $>=$ #3%
}

\lstnewenvironment{bareosConfigResource}[3]{%
% #1 compontent
% #1 component
% #2 resource type
% #3 resource name
\renewcommand*{\lstlistingname}{Resource}
Expand Down
20 changes: 20 additions & 0 deletions manuals/en/main/catmaintenance.tex
Expand Up @@ -1129,6 +1129,26 @@ \subsection{MySQL Temporary Tables}



\subsection{MySQL: Lock Wait Timeout}

In large environments, the Bareos \mysql backend may run in a lock wait timeout.
This can be seen as Bareos message, e.g.:

\begin{bmessage}{Bareos error message because of \mysql lock time timeout}
Fatal error: sql_create.c:899 Fill File table Query failed: INSERT INTO File (FileIndex, JobId, PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT batch.FileIndex, batch.JobId, Path.PathId, Filename.FilenameId,batch.LStat, batch.MD5, batch.DeltaSeq FROM batch JOIN Path ON (batch.Path = Path.Path) JOIN Filename ON (batch.Name = Filename.Name): ERR=Lock wait timeout exceeded; try restarting transaction
\end{bmessage}

In this case the \mysql \configline{innodb_lock_wait_timeout} must be increased.
A value of 300 should be sufficient.

\begin{config}{/etc/my.cnf.d/server.cnf}
...
[mysqld]
innodb_lock_wait_timeout = 300
...
\end{config}



% TODO: hidden, because outdated information. should we improve or remove it?
\hide{
Expand Down

0 comments on commit 0ba27b5

Please sign in to comment.