Extend the lookup timeout to 600 seconds

Code Issues Proposed changes

Changes the default lookup timeout to be 600 seconds which
reduces the risk of lookup failing as a write operation
to the backing database is performed upon lookup thanks to
generation of an agent token.
Overall, this is fairly harmless since by default ramdisks
restart the agent if they were not able to successfully
start.
Change-Id: I35c64c0b4f9b3b607df1bc0c4c2a852aa3595cbd

This commit is contained in:

Julia Kreger

2023年08月24日 08:29:07 -07:00

parent 5ed520df89

commit 4efcce5310

2 changed files with 10 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

9
releasenotes/notes/extend-ipa-lookup-timeout-05ee5b1372792dbe.yaml Normal file

View File

@@ -0,0 +1,9 @@

---

fixes:

- |

The default timeout value for the agent to lookup itself in an Ironic

deployment has been extended to 600 seconds from 300 seconds. This is

to provide better stability for Ironic deployments under heavy load

which may be unable to service new requests. This is particularly true

when the backing database is SQLite for Ironic due to the limited write

concurrency of the database.

Extend the lookup timeout to 600 seconds

9 releasenotes/notes/extend-ipa-lookup-timeout-05ee5b1372792dbe.yaml Normal file Unescape Escape View File

9
releasenotes/notes/extend-ipa-lookup-timeout-05ee5b1372792dbe.yaml Normal file

View File