From a1f1cd853893b70643f0c7971db25fb1336d20a3 Mon Sep 17 00:00:00 2001 From: Joanna Taryma Date: Mon, 6 Mar 2017 14:08:09 -0800 Subject: [PATCH] Fixed release note for DBDeadLock handling Follow up patch of 3428cb74f0a6fe05c23cf00dc66da4c1d9766409 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 --- .../notes/add-db-deadlock-handling-6bc10076537f3727.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/releasenotes/notes/add-db-deadlock-handling-6bc10076537f3727.yaml b/releasenotes/notes/add-db-deadlock-handling-6bc10076537f3727.yaml index d1536407a9..138b0cea4c 100644 --- a/releasenotes/notes/add-db-deadlock-handling-6bc10076537f3727.yaml +++ b/releasenotes/notes/add-db-deadlock-handling-6bc10076537f3727.yaml @@ -1,10 +1,12 @@ --- fixes: - 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: - 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: - All DB API methods doing database writes now retry on deadlock. The ``[database]db_max_retries`` configuration option specifies the maximum