Uploaded image for project: 'mod-users'
  1. mod-users
  2. MODUSERS-152

ExpirationTool retains PostgresClients for removed tenants

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: TBD
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Template:

      Description

      We should consider cleaning up the PostgresClient connections to tenants that no longer exist in the ExpirationTool. If a tenant is removed after being "discovered" by the expiration tool, the PostgresClient will remain in the tenant pool defined in PostgresClient. We could call PostgresClient.closeClient() to clean up the pool after each user expiration execution. By default, user expiration runs every 30 seconds, which seems a bit excessive, and connections expire at 60 seconds, so closing the client, with defaults in place, will affect performance. However, expiration is asynchronous, so performance is not really a priority vs. memory leaks in this case. If we increase the user expiration interval, tenant client pooling may become unnecessary and client closing the right option.

      However solved, we should ensure that when a tenant is removed that we clean up the clients used by the expiration tool.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                adam Adam Dickmeiss
                Reporter:
                mreno Mathew Reno
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases