openstack/mistral
Code Issues Proposed changes

Deprecate api_workers config option

Browse Source 
Since we moved to cheroot, we can't start more than one worker.

Change-Id: Ia3869dec4f4fba6c090050125eee1df17e188427
Signed-off-by: Arnaud M <arnaud.morin@gmail.com>
This commit is contained in:
Arnaud M
2025-08-27 23:52:04 +02:00
parent 2ec6f9c0a7
commit f7dda97d40
2 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
mistral/config.py
View File

@@ -148,6 +148,11 @@ api_opts = [
), ),
cfg.IntOpt( cfg.IntOpt(
'api_workers', 'api_workers',
deprecated_for_removal=True,
deprecated_reason='This option has become useless and mistral-api'
'will start only one worker now. If you want '
'more workers, consider starting mistral-wsgi-api '
'with a wsgi server instead.',
help=_('Number of workers for Mistral API service ' help=_('Number of workers for Mistral API service '
'default is equal to the number of CPUs available if that can ' 'default is equal to the number of CPUs available if that can '
'be determined, else a default worker count of 1 is returned.') 'be determined, else a default worker count of 1 is returned.')

8
releasenotes/notes/remove-api_workers-option-a6210b5f1c0863b6.yaml Normal file
View File

@@ -0,0 +1,8 @@
---
deprecations:
- |
Deprecate the ``api_workers`` option for mistral-api. This option was used
to spawn multiple workers when using oslo.service wsgi server.
Since we moved to cheroot, this is not possible anymore.
If you want to use more than one process to handle Mistral API requests,
you should consider using mistral-wsgi-api behind a wsgi server.