Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
6.1.1
-
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.
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.