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

Table selection doesn't tolerate node failures

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 2.5.23, 6.4.4, 22.08.3
    • 6.4.5, 22.08.4
    • schemarouter
    • None

    Description

      If a table exists on more than one node, the selection of which node the query is routed to ends up choosing the first valid node but not the first valid node for which an open connection exists. This ends up causing problems if a node goes down but a second node would have a copy of that table. This is only of relevance when tables have redundant copies.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.