[jira] [Commented] (ASTERIXDB-1611) AsterixDB + Hyracks daemon threads should have reasonable names

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450992#comment-15450992 ] 

ASF subversion and git services commented on ASTERIXDB-1611:
------------------------------------------------------------

Commit ee3ec00c9cfc28dab7bd80644a6d6a2c68812fc1 in asterixdb's branch refs/heads/master from [~tillw]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=ee3ec00 ]

ASTERIXDB-1611: reasonable names for threads

Change-Id: I3fea28c9e0ea7c3baad1c7a053adabc71bea2a8a
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1092
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mb...@apache.org>


> AsterixDB + Hyracks daemon threads should have reasonable names
> ---------------------------------------------------------------
>
>                 Key: ASTERIXDB-1611
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1611
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Hyracks
>            Reporter: Michael Blow
>            Assignee: Michael Blow
>
> A number of threads are started in AsterixDB that do not have well-named threads.  This hinders the ability to debug / diagnose problems.
> This includes:
> - LogManager.FlushLogsLogger
> - LogFlusher
> - BufferCache.CleanerThread
> - ResultStateSweeper
> - (hyracks.control.common.work.)WorkQueue.WorkerThread
> - (asterix.hyracks.bootstrap.)ClusterWorkExecutor



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)