Fixed release note for DBDeadLock handling
Follow up patch of 3428cb74f0
Add information about db_max_retries configuration option to the
release note. Add periods at the end of senteces in the release note.
Change-Id: I2811ce6976d020e32928773ecb872fefa05e10b7
This commit is contained in:
parent
fec55f4a11
commit
a1f1cd8538
@ -1,10 +1,12 @@
|
|||||||
---
|
---
|
||||||
fixes:
|
fixes:
|
||||||
- Fixes an issue which caused conductor's periodic tasks to stop executing.
|
- Fixes an issue which caused conductor's periodic tasks to stop executing.
|
||||||
See https://bugs.launchpad.net/ironic/+bug/1637210
|
See https://bugs.launchpad.net/ironic/+bug/1637210.
|
||||||
features:
|
features:
|
||||||
- Adds DBDeadlock handling which may improve stability when using Galera.
|
- Adds DBDeadlock handling which may improve stability when using Galera.
|
||||||
See https://bugs.launchpad.net/ironic/+bug/1639338
|
See https://bugs.launchpad.net/ironic/+bug/1639338. Number of retries
|
||||||
|
depends on the configuration option ``[database]db_max_retries`` which
|
||||||
|
programmatically defaults to 5.
|
||||||
upgrade:
|
upgrade:
|
||||||
- All DB API methods doing database writes now retry on deadlock. The
|
- All DB API methods doing database writes now retry on deadlock. The
|
||||||
``[database]db_max_retries`` configuration option specifies the maximum
|
``[database]db_max_retries`` configuration option specifies the maximum
|
||||||
|
Loading…
Reference in New Issue
Block a user