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

Internal error: MCS-2004: Cannot connect to ExeMgr | Message Improved

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • PrimProc
    • None

    Description

      As a user, this error message is extremely frustrating, confusing and unclear.
      What is the user supposed to do.
      Today you need to be sherlock holmes in determining what went wrong and what do to next, often bogging down support then escalated to developers, which takes time to triage.

      ERROR 1815 (HY000): Internal error: MCS-2004: Cannot connect to ExeMgr.

      Idea:
      split error message in two ( plugin error vs ddl/dml proc errors )
      potential: 

      ERROR 1815 (HY000): Internal error: MCS-2004: Cannot connect to ExeMgr. Please check every node is running primproc process, consider restarting columnstore if this error persists.

      ddl/dml proc errors: suggest restarting mariadb
      or maybe an analyze tool to report back the health of each subprocess and the error reference to use the tool
      ask drrtuy for additional ideas

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MCOL-5877 New User Experience Challenges

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              allen.herrera Allen Herrera
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.