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

Authentication data should be thread specific

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.1
    • 2.2.2
    • N/A
    • None
    • 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

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

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.