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

ExeMgr and PrimProc reconnect

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.5.3
    • Icebox
    • ExeMgr, PrimProc
    • 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

              Unassigned Unassigned
              David.Hall David Hall (Inactive)
              Votes:
              1 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.