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

Columnstore configuration file left in a bad state after user enables local query, then disable feature

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 1.1.5
    • 1.1.0
    • installation
    • None

    Description

      A customer reported an issue with memory over usage and the system restarting due to pm2 swapping. Issue was the exemgr was incorrectly running on pm2 and utilizing memory.

      Jun 22 10:27:25 usfit-scdocker2 ServerMonitor[10835]: 25.593968 |0|0|0| I 09 CAL0000: Memory Usage for Process: PrimProc : Memory Used 4011534 : % Used 31
      Jun 22 10:27:25 usfit-scdocker2 ServerMonitor[10835]: 25.594002 |0|0|0| I 09 CAL0000: Memory Usage for Process: ExeMgr : Memory Used 5919714 : % Used 45

      The problem turned out to be that the user configured the system with 'local query' feature enabled which added additional exemgr entries in the Columnstore.xml. But then they ran postConfigure again and selected disable of the 'local query' feature, but the entroes didnt get removed from the COlumnstore.xml

      this from a system that had 1um and 2 pm

      <ExeMgr2>
      <IPAddr>192.168.212.33</IPAddr>
      <Port>8601</Port>
      <Module>pm1</Module>
      </ExeMgr2>
      <ExeMgr3>
      <IPAddr>192.168.212.34</IPAddr>
      <Port>8601</Port>
      <Module>pm2</Module>
      </ExeMgr3>

      Attachments

        Activity

          People

            Unassigned Unassigned
            hill David Hill (Inactive)
            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.