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

ExeMgr and PrimProc reconnect

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.5.3
    • Fix Version/s: 5.6.1
    • Component/s: ExeMgr, PrimProc
    • Labels:
      None

      Description

      Currently, ExeMgr and PrimProc don't attempt to reconnect after comm failure. Specifically after one or the other Segv. ProcMon currently sees the failure of one or the other and restarts both. This is clumsy. With the move of control to other mechanisms, asking them to do this is unreasonable. In addition, if the com just happens to fail temporarily, there may be no attempt to restart, and certainly no attempt to reconnect

      This Jira is to create awareness of the comm state and automatic reconnect between the two processes.

      A check of other procerss, such as DMProc and DDLProc needs to also be done. The problem may be more widespread.

      The solution may be to create a class for all processes to use to help re-establish connections.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              David.Hall David Hall
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: