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

["Peter Bacsko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Bacsko updated OOZIE-2603:
--------------------------------
    Attachment: OOZIE-2603-001.patch

> 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
>         Attachments: OOZIE-2603-001.patch
>
>
> 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)