You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Cseh (JIRA)" <ji...@apache.org> on 2016/07/05 10:05:11 UTC

[jira] [Comment Edited] (OOZIE-2603) Give thread pools a meaningful name (CallableQueueService, SchedulerService)

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

Peter Cseh edited comment on OOZIE-2603 at 7/5/16 10:04 AM:
------------------------------------------------------------

+1 for the idea it would be useful during test debug to know which thread is the source of an action.


was (Author: gezapeti):
+1 (nonbinding) it would be useful during test debug to know which thread is the source of an action.

> Give thread pools a meaningful name (CallableQueueService, SchedulerService)
> ----------------------------------------------------------------------------
>
>                 Key: OOZIE-2603
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2603
>             Project: Oozie
>          Issue Type: Bug
>          Components: core
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Minor
>
> In Oozie, we have two thread pools. One is used by SchedulerService and another is used by CallableQueueService. These are named something like pool-X-thread-Y.
> Even though thread names are not logged (usually), it can still be useful in case of thread dumps and tests, where we can see where a particular XCommand is executed (see OOZIE-2564).
> Suggested names:
> * CallableQueueService: CallableQueue-thread-N (or just CallableQueue-N)
> * Scheduler: Scheduler-thread-N (or just Scheduler-N)



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