Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-4770

Distribute queries processing b/w ExeMgrs/primprocs in the cluster.

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 6.1.1
    • cmapi-22.08.1
    • cmapi
    • None
    • 2021-9

    Description

      Despite the fact CMAPI starts ExeMgr on every cluster node the Columnstore.xml contains a description of a single ExeMgr that resides at the primary only.
      The preliminary testing in AWS demonstrates 20% performance improvement if there workload is distributed across multiple EMs so CMAPI now adds a new ExeMgr section for every node added into the cluster and removes it when the node is deleted.

      Attachments

        Issue Links

          Activity

            drrtuy Roman added a comment -

            4QA Previously any MDB in the cluster uses a single EM that resides at the primary. With this patch the queries issued at the node using a local MDB goes through the local EM only. One can monitor cpu utilization using top at non primary nodes running queries using the node's MDB.

            drrtuy Roman added a comment - 4QA Previously any MDB in the cluster uses a single EM that resides at the primary. With this patch the queries issued at the node using a local MDB goes through the local EM only. One can monitor cpu utilization using top at non primary nodes running queries using the node's MDB.
            drrtuy Roman added a comment -

            With this patch the queries issued at the node are processed with the local EM only.
            Talking about the schema replication you missed the point that MaxScale takes care about schema replication in normal installation.

            drrtuy Roman added a comment - With this patch the queries issued at the node are processed with the local EM only. Talking about the schema replication you missed the point that MaxScale takes care about schema replication in normal installation.

            Build tested: 6.1.1 ( Drone #2635 )

            Executing a query on any node uses the ExeMgr on the same node and covers data for the entire database (not just data on the local node, as "local query" used to do)
            Columnstore.xml updated fine when removing and adding nodes.

            dleeyh Daniel Lee (Inactive) added a comment - Build tested: 6.1.1 ( Drone #2635 ) Executing a query on any node uses the ExeMgr on the same node and covers data for the entire database (not just data on the local node, as "local query" used to do) Columnstore.xml updated fine when removing and adding nodes.

            Build verified: 22.08-1 (#5324), cmapi-22.08-1 (#743)

            Verified installation and cmapi operations:

            Using this build of the cmapi, installed 5.6.1-1, 6.4.4-2, and 22.08-1 on VMs
            installed 6.4.4-2, and 22.08-1 on docker containers.

            dleeyh Daniel Lee (Inactive) added a comment - Build verified: 22.08-1 (#5324), cmapi-22.08-1 (#743) Verified installation and cmapi operations: Using this build of the cmapi, installed 5.6.1-1, 6.4.4-2, and 22.08-1 on VMs installed 6.4.4-2, and 22.08-1 on docker containers.

            People

              dleeyh Daniel Lee (Inactive)
              drrtuy Roman
              Votes:
              0 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.