Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
-
2021-8, 2021-9
Description
To describe a connection from UM to PM one needs to add a section into Columnstore.xml like this for every connection
<PMS1>
|
<IPAddr>127.0.0.1</IPAddr>
|
<Port>8620</Port>
|
</PMS1>
|
If the number of connections is significant it might be tedious to describe them and wasteful to store them in the config.
The suggested way to describe now is to add a single section per PM exists in the cluster and set PrimitiveServers.ConnectionsPerPrimProc to describe how many PM-EM connections must be created by DEC::Setup() method.
It is worth to note the issue will also cover CMAPI part that manipulates the XML configuration adding or removing a node from the cluster.
Attachments
Issue Links
- is caused by
-
MCOL-4593 Multiple concurrent queries with aggregates are bottlenecked, result in lack of user scalability
-
- Stalled
-
Build tested: 6.1.1 ( Drone #2640), CMAPI ( Drone #502 )
CMAPI DELETE is not update PMS<x> in Columnstore.xml correctly
after installation
<PMS1>
<IPAddr>s1pm1</IPAddr>
<Port>8620</Port>
</PMS1>
<PMS2>
<IPAddr>s1pm2</IPAddr>
<Port>8620</Port>
</PMS2>
<PMS3>
<IPAddr>s1pm3</IPAddr>
<Port>8620</Port>
</PMS3>
After deleting node s1pm3
There should be 1 entry per PM, a total of 2
But there are 2 entries per PM, a total of 4
<PMS1>
<IPAddr>s1pm1</IPAddr>
<Port>8620</Port>
</PMS1>
<PMS2>
<IPAddr>s1pm2</IPAddr>
<Port>8620</Port>
</PMS2>
<PMS3>
<IPAddr>s1pm1</IPAddr>
<Port>8620</Port>
</PMS3>
<PMS4>
<IPAddr>s1pm2</IPAddr>
<Port>8620</Port>
</PMS4>
After putting back node s1pm3
<PMS1>
<IPAddr>s1pm1</IPAddr>
<Port>8620</Port>
</PMS1>
<PMS2>
<IPAddr>s1pm2</IPAddr>
<Port>8620</Port>
</PMS2>
<PMS3>
<IPAddr>s1pm3</IPAddr>
<Port>8620</Port>
</PMS3>