373cbdbda8
Though we can now set ``connect_retires`` while creating an adapter object, that would allow retries in case of connection timeout (ex. with session clients derived from Adapater/LegacyJsonAdapater), it can't be used in certain scenarios like endpoint discovery with auth plugin get_discovery() or getting AccessInfo with get_access()/get_auth_ref(). Having ``connect_retries`` in Session constructor would allow users with option of setting it when creating session objects (if they want) and can be overridden per service with the adapter interface. This commit also changes the default value of ``connect_retries`` from 0 to None to allow for adapter's to override retries on the session object. Depends-On: https://review.opendev.org/#/c/680497/ Change-Id: Iffb671fefae23926b1f09017d9db438341eae238 Partial-Bug: #1840235
12 lines
586 B
YAML
12 lines
586 B
YAML
---
|
|
features:
|
|
- |
|
|
[`feature bug 1840235 <https://bugs.launchpad.net/keystoneauth/+bug/1840235>`_]
|
|
Adds ``connect_retries`` to Session.__init__(), that can then be used
|
|
by projects when creating session objects, to set the required number of
|
|
retries for new connection requests. This would specifically help avoid
|
|
a scalability issue that results in number of ConnectTimeout errors when
|
|
doing endpoint discovery and fetching roles using an auth plugin under
|
|
heavy load. This still allows for it to be overridden per service with
|
|
the adapter interface.
|