Bug #17445

Weblate: tune VM resources and service config for better performance

Added by zen 2020-01-17 15:49:51 . Updated 2020-04-22 15:50:31 .

Status:
Rejected
Priority:
Elevated
Assignee:
Sysadmins
Category:
Infrastructure
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Translation Platform
Deliverable for:

Description

Weblate is having recurrent issues with database timeouts such as:

2020-01-16 09:56:45,547 ERROR Internal Server Error: /translate/tails/thedaywefightback/it/
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.5/dist-packages/django/db/backends/mysql/base.py", line 101, in execute
    return self.cursor.execute(query, args)
  File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 226, in execute
    self.errorhandler(self, exc, value)
  File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorvalue
  File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 217, in execute
    res = self._query(query)
  File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 378, in _query
    rowcount = self._do_query(q)
  File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 341, in _do_query
    db.query(q)
  File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 280, in query
    _mysql.connection.query(self, query)
_mysql_exceptions.OperationalError: (1205, 'Lock wait timeout exceeded; try restarting transaction')

This may be related with what is described in the upstream issue (also linked in the description of Bug #16994), which describes performance problems with the use of an “external full text engine” and links to other issues that describe memory exhaustion and timeout problems because of this.

This issue should be part of a larger combo together with (1) upgrade to latest Weblate (Feature #17345) and (2) switch to PostgreSQL (Bug #16994). This way we’d mitigate current problems and also be ready to welcome new performance-related features when they are available in Weblate.


Subtasks


Related issues

Related to Tails - Feature #17345: Upgrade Weblate to 3.9+ Confirmed
Related to Tails - Bug #16994: Weblate database switch to PostgreSQL Resolved 2020-04-01 2020-04-01
Related to Tails - Bug #17446: Weblate: Failed to fetch translations from Weblate Translation Memory Confirmed

History

#1 Updated by zen 2020-01-17 15:50:52

#2 Updated by zen 2020-01-17 15:51:04

  • related to Bug #16994: Weblate database switch to PostgreSQL added

#3 Updated by zen 2020-01-17 16:04:10

  • related to Bug #17446: Weblate: Failed to fetch translations from Weblate Translation Memory added

#4 Updated by hefee 2020-04-22 15:50:31

  • Status changed from Confirmed to Rejected

We use a PostgeSQL database now, so this issue doesn’t make sense to keep open as it is to much mysql specific.