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

Simplify configuration of EM to PM connections

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 6.1.1
    • ExeMgr
    • 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

          Activity

            dleeyh Daniel Lee (Inactive) added a comment - - edited

            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>
            

            dleeyh Daniel Lee (Inactive) added a comment - - edited 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>

            Build tested: 6.1.1 ( Drone #2640), CMAPI ( Drone #502 )

            Number of connections don't seem to be correspond to what's configured.
            Used "ss -tenp |grep PrimProc"

            After installation
            ConnectionsPerPrimProc=2
            pm1=7
            pm2=10
            pm3=7

            After change
            ConnectionsPerPrimProc=5
            pm1=7
            pm2=21
            pm3=7

            dleeyh Daniel Lee (Inactive) added a comment - Build tested: 6.1.1 ( Drone #2640), CMAPI ( Drone #502 ) Number of connections don't seem to be correspond to what's configured. Used "ss -tenp |grep PrimProc" After installation ConnectionsPerPrimProc=2 pm1=7 pm2=10 pm3=7 After change ConnectionsPerPrimProc=5 pm1=7 pm2=21 pm3=7
            drrtuy Roman added a comment -

            dleeyh The command 'ss -tenp |grep PrimProc' returns all connections that has a line PrimProc so there are additional connections at PP2. If you checked its output right after adding a node it is clear that some of EM to PP connections were not established and you need to run any query that re-establish all connections that EM couldn't create on its startup.

            drrtuy Roman added a comment - dleeyh The command 'ss -tenp |grep PrimProc' returns all connections that has a line PrimProc so there are additional connections at PP2. If you checked its output right after adding a node it is clear that some of EM to PP connections were not established and you need to run any query that re-establish all connections that EM couldn't create on its startup.
            drrtuy Roman added a comment -

            The issue with a number of PMS sections on node removal had been fixed. The connections number factor had been explained earlier.

            drrtuy Roman added a comment - The issue with a number of PMS sections on node removal had been fixed. The connections number factor had been explained earlier.

            Build verified: 6.1.1 ( Drone #2687), CMAPI ( Drone #505 )

            dleeyh Daniel Lee (Inactive) added a comment - Build verified: 6.1.1 ( Drone #2687), CMAPI ( Drone #505 )

            People

              dleeyh Daniel Lee (Inactive)
              drrtuy Roman
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.