Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-35080

replace global refresh sync lock in OIDC provider with per-refresh-token one

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.15
    • Management Console
    • None
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the global sync lock that applied to all HTTP-serving spawned gorotines with a sync lock that is specific to each of the refresh tokens. With this update, the global refresh sync lock on a cluster with an external OIDC environment was replaced with per-refresh token one. As a result, refresh token performance is improved by 30 to 50%. (link:https://issues.redhat.com/browse/OCPBUGS-35080[*OCPBUGS-35080*])
      Show
      * Previously, the global sync lock that applied to all HTTP-serving spawned gorotines with a sync lock that is specific to each of the refresh tokens. With this update, the global refresh sync lock on a cluster with an external OIDC environment was replaced with per-refresh token one. As a result, refresh token performance is improved by 30 to 50%. (link: https://issues.redhat.com/browse/OCPBUGS-35080 [* OCPBUGS-35080 *])
    • Enhancement
    • Done

      In a cluster with external OIDC environment we need to replace global refresh sync lock in OIDC provider with per-refresh-token one. The work should replace the sync lock that would apply to all HTTP-serving spawned goroutines with a sync-lock that is specific to each of the refresh tokens

      Description of problem:

      Version-Release number of selected component (if applicable):

      Steps to Reproduce:

      Actual results:

      Expected results:

          That reduces token refresh request handling time by about 30%.

      Additional info:

              slaznick@redhat.com Stanislav Láznička (Inactive)
              jhadvig@redhat.com Jakub Hadvig
              Yanping Zhang Yanping Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: