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

MaxScale ID in replication_heartbeat table is not unique enough

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 1.2.1
    • N/A
    • mariadbmon
    • None

    Description

      MaxScale will use the PID of the running process to identify each MaxScale instance. This might be enough for multiple MaxScales running on the same system but MaxScales running on different systems can have multiple processes with the same PID.

      MaxScale needs to use an identifier that is unique to the process and unique to the system MaxScale is running in.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            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.