File: handle-mariadb-transactional-error-d84c95cdb4d3b27f.yaml

package info (click to toggle)
python-oslo.db 17.2.1-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,296 kB
  • sloc: python: 10,081; sh: 33; makefile: 25
file content (23 lines) | stat: -rw-r--r-- 1,231 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
---
features:
  - |
    Added support for detecting and handling MariaDB error 1020 "Record has
    changed since last read" which occurs under REPEATABLE-READ isolation
    level when MariaDB detects that a row has changed since it was last read
    in the current transaction. This error is now wrapped in a new
    ``DBConsistencyError`` exception class that inherits from ``DBDeadlock``,
    ensuring that existing retry decorators and error handling code will
    automatically handle this transient concurrency condition.
fixes:
  - |
    Fixed handling of MariaDB error 1020 that was previously not properly
    categorized by oslo.db's exception filtering system. This error, which
    can occur in OpenStack services like Nova and Keystone when using MariaDB
    with REPEATABLE-READ isolation level, is now properly wrapped in a
    ``DBConsistencyError`` exception (a subclass of ``DBDeadlock``) instead
    of being passed through as a generic ``OperationalError``. This ensures
    that existing retry mechanisms that handle deadlock-like conditions will
    automatically work with this MariaDB-specific consistency error.

    For more details, see `bug 2116186
    <https://bugs.launchpad.net/nova/+bug/2116186>`_.