[ https://issues.apache.org/jira/browse/ASTERIXDB-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534685#comment-15534685 ]
ASF subversion and git services commented on ASTERIXDB-1611: ------------------------------------------------------------ Commit 102ef590b1475731732feadf8c7e7302b7bb9968 in asterixdb's branch refs/heads/master from [~mblow] [ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=102ef59 ] ASTERIXDB-1611: Improve Thread Names Executor threads are now named as follows: - "Executor-<thread number>:<nodeId|ClusterController>" Change-Id: Iea54740c51a9ac9388337cf88260a8482ff4a334 Reviewed-on: https://asterix-gerrit.ics.uci.edu/1226 Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Reviewed-by: Till Westmann <ti...@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)