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

OAM Process failover logic for DDLproc is incorrect - causing DDL to stop working

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.1.5
    • 1.1.7
    • ?
    • None
    • 2 um 3 pm system on redhat 7
    • 2018-14, 2018-15, 2018-16, 2018-17

    Description

      Customer reproted problems with DDl commands create table failing. Investigation showed that DDLproc ip address was pointing to incorrect UM module, it was pointing to UM2. Should have been pointing to UM1.

      issue caused by OAM process failover logic.

      its a DDLproc crash and failover... DDLproc um1 is crashing and we are trying to start DDMLproc on um2... that is changing the IP...

      Jun 28 23:57:12 x01sibgadb3a ProcessMonitor[7877]: 12.138592 |0|0|0| D 18 CAL0000: statusControl: Set Process um1/DDLProc State = AUTO_OFFLINE PID = 0

      Jun 28 23:57:13 x01sibgadb3a ProcessManager[8303]: 13.192889 |0|0|0| D 17 CAL0000: setPMProcIPs called for um2
      Jun 28 23:57:13 x01sibgadb3a ProcessManager[8303]: 13.195507 |0|0|0| D 17 CAL0000: setPMProcIPs: DDLProc to 10.91.134.124

      Attachments

        Activity

          People

            dleeyh Daniel Lee (Inactive)
            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.