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

Adding get_lock and release_lock support

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0, 2.1.12
    • Fix Version/s: 2.2.2
    • Component/s: QueryClassifier
    • Labels:
      None

      Description

      Currently the features below are not supported when we use maxscale and a router that can end up on multiple servers.
      GET_LOCK()
      RELEASE_LOCK()
      IS_FREE_LOCK()
      IS_USED_LOCK()

      If we do a get_lock and get routed to serverA and later on we do a release_lock and this is routed to serverB the lock on serverA is never released.
      It can be used if force the router to always go to the master server.

      Because of this we can not use the readwrite split router.

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            Maikel Punie Maikel Punie
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: