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

Queries on already established connections hanging for 15min when Redis server disconnected hard

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.2.4
    • Fix Version/s: 6.4.0
    • Component/s: cache
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-157, MXS-SPRINT-158

      Description

      In a test setup with Maxscale and Redis on separate VMs shutting down the Redis service, or even killing the redis-server process the hard way with "kill -9", does not affect Maxscale and its clients that much, queries are just being sent right to a backend server each time without caching.

      When powering off the whole Redis VM on the other hand so that the TCP connection to Redis is still open and just inactive from the Maxscale perspective already established client sessions hang on the next query they try to execute until finally running into a timeout.

      The same would probably also happen when having a network failure between Maxscale and Redis servers.

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            hholzgra Hartmut Holzgraefe
            Votes:
            1 Vote for this issue
            Watchers:
            4 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.