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

The status of an Exasol or GridGain service does not reflect whether Exasol or GridGain can be reached

    XMLWordPrintable

Details

    • Bug
    • Status: In Review (View Workflow)
    • Major
    • Resolution: Unresolved
    • 25.10, 26.10
    • 26.10.1
    • None
    • None

    Description

      The status of a service using the Exasol or GridGain router is set when MaxScale starts and never changes, so the service appears to be running also when Exasol or GridGain cannot be reached. Consequently SmartRouter keeps connecting to it, and each attempt takes until the ODBC login timeout to fail. A failure to connect is also reported as permanent, so SmartRouter does not use the target again in that session, even if it becomes available.

      Attachments

        Issue Links

          Activity

            People

              johan.wikman Johan Wikman
              johan.wikman Johan Wikman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - 1d Original Estimate - 1d
                  1d
                  Remaining:
                  Time Spent - 7.5h Remaining Estimate - 1h
                  1h
                  Logged:
                  Time Spent - 7.5h Remaining Estimate - 1h
                  7.5h

                  Git Integration

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