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

There is no way to identify execution thread that causes bottleneck

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.2.2
    • 1.2.4
    • ExeMgr, PrimProc
    • None
    • 2019-03

    Description

      There is no way to identify threads of execution in runtime so here is the patch to explicitly name threads. Any additional changes that helps to identify execution threads are welcome.

      Attachments

        Activity

          Transition Time In Source Status Execution Times
          Roman made transition -
          Open Confirmed
          		11s 1
          Roman made transition -
          Confirmed In Review
          		2h 36m 1
          Patrick LeBlanc (Inactive) made transition -
          In Review In Testing
          		2h 10m 1
          Zdravelina Sokolovska (Inactive) made transition -
          In Testing Closed
          		14d 2h 55m 1

          People

            winstone Zdravelina Sokolovska (Inactive)
            drrtuy Roman
            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.