Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-1539

Authentication data should be thread specific

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.2.2
    • Component/s: N/A
    • Labels:
      None
    • Sprint:
      2017-49

      Description

      Currently the authentication data is stored in a sqlite database that is opened in serialized mode. If clients connect and disconnect in rapid fashion this will cause contention between the worker threads, which will degrade the overall performance.

      Instead, each thread should maintain its own database of authentication data, so that the user authentication causes no cross-thread interaction. The data need not be persisted as the user data is anyway always refreshed when MaxScale starts.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            johan.wikman Johan Wikman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: